Package: mka142-apprise
ap·prise/verbTo inform or tell (someone). To make one aware of something.Appriseallows you to send a notification toalmostall of the most popularnotificationservices available to us today such as: Telegram, Discord, Slack, Amazon SNS, Gotify, etc.One notification library to rule them all.A common and intuitive notification syntax.Supports the handling of images and attachments (to the notification services that will accept them).It's incredibly lightweight.Amazing response times because all messages sent asynchronously.Developers who wish to provide a notification service no longer need to research each and every one out there. They no longer need to try to adapt to the new ones that comeout thereafter. They just need to include this one library and then they can immediately gain access to almost all of the notifications services available to us today.System Administrators and DevOps who wish to send a notification now no longer need to find the right tool for the job. Everything is already wrapped and supported within theapprisecommand line tool (CLI) that ships with this product.Supported NotificationsThe section identifies all of the services supported by this library.Check out the wiki for more information on the supported modules here.Popular Notification ServicesThe table below identifies the services this tool supports and some example service urls you need to use in order to take advantage of it. Click on any of the services listed below to get more details on how you can configure Apprise to access them.Notification ServiceService IDDefault PortExample SyntaxBoxcarboxcar://(TCP) 443boxcar://hostnameboxcar://hostname/@tagboxcar://hostname/device_tokenboxcar://hostname/device_token1/device_token2/device_tokenNboxcar://hostname/@tag/@tag2/device_tokenDiscorddiscord://(TCP) 443discord://webhook_id/webhook_tokendiscord://avatar@webhook_id/webhook_tokenEmbyemby:// or embys://(TCP) 8096emby://user@hostname/emby://user:password@hostnameEnigma2enigma2:// or enigma2s://(TCP) 80 or 443enigma2://hostnameFaastfaast://(TCP) 443faast://authorizationtokenFCMfcm://(TCP) 443fcm://project@apikey/DEVICE_IDfcm://project@apikey/#TOPICfcm://project@apikey/DEVICE_ID1/#topic1/#topic2/DEVICE_ID2/Flockflock://(TCP) 443flock://tokenflock://botname@tokenflock://app_token/u:useridflock://app_token/g:channel_idflock://app_token/u:userid/g:channel_idGittergitter://(TCP) 443gitter://token/roomgitter://token/room1/room2/roomNGoogle Chatgchat://(TCP) 443gchat://workspace/key/tokenGotifygotify:// or gotifys://(TCP) 80 or 443gotify://hostname/tokengotifys://hostname/token?priority=highGrowlgrowl://(UDP) 23053growl://hostnamegrowl://hostname:portnogrowl://password@hostnamegrowl://password@hostname:portNote: you can also use the get parameterversionwhich can allow the growl request to behave using the older v1.x protocol. An example would look like: growl://hostname?version=1Home Assistanthassio:// or hassios://(TCP) 8123 or 443hassio://hostname/accesstokenhassio://user@hostname/accesstokenhassio://user:password@hostname:port/accesstokenhassio://hostname/optional/path/accesstokenIFTTTifttt://(TCP) 443ifttt://webhooksID/Eventifttt://webhooksID/Event1/Event2/EventNifttt://webhooksID/Event1/?+Key=Valueifttt://webhooksID/Event1/?-Key=value1Joinjoin://(TCP) 443join://apikey/devicejoin://apikey/device1/device2/deviceN/join://apikey/groupjoin://apikey/groupA/groupB/groupNjoin://apikey/DeviceA/groupA/groupN/DeviceN/KODIkodi:// or kodis://(TCP) 8080 or 443kodi://hostnamekodi://user@hostnamekodi://user:password@hostname:portKumuloskumulos://(TCP) 443kumulos://apikey/serverkeyLaMetric Timelametric://(TCP) 443lametric://apikey@device_ipaddrlametric://apikey@hostname:portlametric://client_id@client_secretMailgunmailgun://(TCP) 443mailgun://user@hostname/apikeymailgun://user@hostname/apikey/emailmailgun://user@hostname/apikey/email1/email2/emailNmailgun://user@hostname/apikey/?name="From%20User"Matrixmatrix:// or matrixs://(TCP) 80 or 443matrix://hostnamematrix://user@hostnamematrixs://user:pass@hostname:port/#room_aliasmatrixs://user:pass@hostname:port/!room_idmatrixs://user:pass@hostname:port/#room_alias/!room_id/#room2matrixs://token@hostname:port/?webhook=matrixmatrix://user:token@hostname/?webhook=slack&format=markdownMattermostmmost:// or mmosts://(TCP) 8065mmost://hostname/authkeymmost://hostname:80/authkeymmost://user@hostname:80/authkeymmost://hostname/authkey?channel=channelmmosts://hostname/authkeymmosts://user@hostname/authkeyMicrosoft Teamsmsteams://(TCP) 443msteams://TokenA/TokenB/TokenC/Nextcloudncloud:// or nclouds://(TCP) 80 or 443ncloud://adminuser:pass@host/Usernclouds://adminuser:pass@host/User1/User2/UserNNoticanotica://(TCP) 443notica://Token/Notificonotifico://(TCP) 443notifico://ProjectID/MessageHook/Office 365o365://(TCP) 443o365://TenantID:AccountEmail/ClientID/ClientSecreto365://TenantID:AccountEmail/ClientID/ClientSecret/TargetEmailo365://TenantID:AccountEmail/ClientID/ClientSecret/TargetEmail1/TargetEmail2/TargetEmailNOneSignalonesignal://(TCP) 443onesignal://AppID@APIKey/PlayerIDonesignal://TemplateID:AppID@APIKey/UserIDonesignal://AppID@APIKey/#IncludeSegmentonesignal://AppID@APIKey/EmailOpsgenieopsgenie://(TCP) 443opsgenie://APIKeyopsgenie://APIKey/UserIDopsgenie://APIKey/#Teamopsgenie://APIKey/*Scheduleopsgenie://APIKey/^EscalationParsePlatformparsep:// or parseps://(TCP) 80 or 443parsep://AppID:MasterKey@Hostnameparseps://AppID:MasterKey@HostnamePopcornNotifypopcorn://(TCP) 443popcorn://ApiKey/ToPhoneNopopcorn://ApiKey/ToPhoneNo1/ToPhoneNo2/ToPhoneNoN/popcorn://ApiKey/ToEmailpopcorn://ApiKey/ToEmail1/ToEmail2/ToEmailN/popcorn://ApiKey/ToPhoneNo1/ToEmail1/ToPhoneNoN/ToEmailNProwlprowl://(TCP) 443prowl://apikeyprowl://apikey/providerkeyPushBulletpbul://(TCP) 443pbul://accesstokenpbul://accesstoken/#channelpbul://accesstoken/A_DEVICE_IDpbul://accesstoken/email@address.compbul://accesstoken/#channel/#channel2/email@address.net/DEVICEPushjetpjet:// or pjets://(TCP) 80 or 443pjet://hostname/secretpjet://hostname:port/secretpjets://secret@hostname/secretpjets://hostname:port/secretPush (Techulus)push://(TCP) 443push://apikey/Pushedpushed://(TCP) 443pushed://appkey/appsecret/pushed://appkey/appsecret/#ChannelAliaspushed://appkey/appsecret/#ChannelAlias1/#ChannelAlias2/#ChannelAliasNpushed://appkey/appsecret/@UserPushedIDpushed://appkey/appsecret/@UserPushedID1/@UserPushedID2/@UserPushedIDNPushoverpover://(TCP) 443pover://user@tokenpover://user@token/DEVICEpover://user@token/DEVICE1/DEVICE2/DEVICENNote: you must specify both your user_id and tokenPushSaferpsafer:// or psafers://(TCP) 80 or 443psafer://privatekeypsafers://privatekey/DEVICEpsafer://privatekey/DEVICE1/DEVICE2/DEVICENRedditreddit://(TCP) 443reddit://user:password@app_id/app_secret/subredditreddit://user:password@app_id/app_secret/sub1/sub2/subNRocket.Chatrocket:// or rockets://(TCP) 80 or 443rocket://user:password@hostname/RoomID/Channelrockets://user:password@hostname:443/#Channel1/#Channel1/RoomIDrocket://user:password@hostname/#Channelrocket://webhook@hostnamerockets://webhook@hostname/@User/#ChannelRyverryver://(TCP) 443ryver://Organization/Tokenryver://botname@Organization/TokenSendGridsendgrid://(TCP) 443sendgrid://APIToken:FromEmail/sendgrid://APIToken:FromEmail/ToEmailsendgrid://APIToken:FromEmail/ToEmail1/ToEmail2/ToEmailN/SimplePushspush://(TCP) 443spush://apikeyspush://salt:password@apikeyspush://apikey?event=AppriseSlackslack://(TCP) 443slack://TokenA/TokenB/TokenC/slack://TokenA/TokenB/TokenC/Channelslack://botname@TokenA/TokenB/TokenC/Channelslack://user@TokenA/TokenB/TokenC/Channel1/Channel2/ChannelNSMTP2Gosmtp2go://(TCP) 443smtp2go://user@hostname/apikeysmtp2go://user@hostname/apikey/emailsmtp2go://user@hostname/apikey/email1/email2/emailNsmtp2go://user@hostname/apikey/?name="From%20User"SparkPostsparkpost://(TCP) 443sparkpost://user@hostname/apikeysparkpost://user@hostname/apikey/emailsparkpost://user@hostname/apikey/email1/email2/emailNsparkpost://user@hostname/apikey/?name="From%20User"Spontitspontit://(TCP) 443spontit://UserID@APIKey/spontit://UserID@APIKey/Channelspontit://UserID@APIKey/Channel1/Channel2/ChannelNSyslogsyslog://n/asyslog://syslog://FacilityTelegramtgram://(TCP) 443tgram://bottoken/ChatIDtgram://bottoken/ChatID1/ChatID2/ChatIDNTwittertwitter://(TCP) 443twitter://CKey/CSecret/AKey/ASecrettwitter://user@CKey/CSecret/AKey/ASecrettwitter://CKey/CSecret/AKey/ASecret/User1/User2/User2twitter://CKey/CSecret/AKey/ASecret?mode=tweetTwisttwist://(TCP) 443twist://pasword:logintwist://password:login/#channeltwist://password:login/#team:channeltwist://password:login/#team:channel1/channel2/#team3:channelXBMCxbmc:// or xbmcs://(TCP) 8080 or 443xbmc://hostnamexbmc://user@hostnamexbmc://user:password@hostname:portXMPPxmpp:// or xmpps://(TCP) 5222 or 5223xmpp://password@hostnamexmpp://user:password@hostnamexmpps://user:password@hostname:port?jid=user@hostname/resourcexmpps://password@hostname/target@myhost, target2@myhost/resourceWebex Teams (Cisco)wxteams://(TCP) 443wxteams://TokenZulip Chatzulip://(TCP) 443zulip://botname@Organization/Tokenzulip://botname@Organization/Token/Streamzulip://botname@Organization/Token/EmailSMS Notification SupportNotification ServiceService IDDefault PortExample SyntaxAWS SNSsns://(TCP) 443sns://AccessKeyID/AccessSecretKey/RegionName/+PhoneNosns://AccessKeyID/AccessSecretKey/RegionName/+PhoneNo1/+PhoneNo2/+PhoneNoNsns://AccessKeyID/AccessSecretKey/RegionName/Topicsns://AccessKeyID/AccessSecretKey/RegionName/Topic1/Topic2/TopicNClickSendclicksend://(TCP) 443clicksend://user:pass@PhoneNoclicksend://user:pass@ToPhoneNo1/ToPhoneNo2/ToPhoneNoND7 Networksd7sms://(TCP) 443d7sms://user:pass@PhoneNod7sms://user:pass@ToPhoneNo1/ToPhoneNo2/ToPhoneNoNDingTalkdingtalk://(TCP) 443dingtalk://token/dingtalk://token/ToPhoneNodingtalk://token/ToPhoneNo1/ToPhoneNo2/ToPhoneNo1/Kavenegarkavenegar://(TCP) 443kavenegar://ApiKey/ToPhoneNokavenegar://FromPhoneNo@ApiKey/ToPhoneNokavenegar://ApiKey/ToPhoneNo1/ToPhoneNo2/ToPhoneNoNMessageBirdmsgbird://(TCP) 443msgbird://ApiKey/FromPhoneNomsgbird://ApiKey/FromPhoneNo/ToPhoneNomsgbird://ApiKey/FromPhoneNo/ToPhoneNo1/ToPhoneNo2/ToPhoneNoN/MSG91msg91://(TCP) 443msg91://AuthKey/ToPhoneNomsg91://SenderID@AuthKey/ToPhoneNomsg91://AuthKey/ToPhoneNo1/ToPhoneNo2/ToPhoneNoN/Nexmonexmo://(TCP) 443nexmo://ApiKey:ApiSecret@FromPhoneNonexmo://ApiKey:ApiSecret@FromPhoneNo/ToPhoneNonexmo://ApiKey:ApiSecret@FromPhoneNo/ToPhoneNo1/ToPhoneNo2/ToPhoneNoN/Sinchsinch://(TCP) 443sinch://ServicePlanId:ApiToken@FromPhoneNosinch://ServicePlanId:ApiToken@FromPhoneNo/ToPhoneNosinch://ServicePlanId:ApiToken@FromPhoneNo/ToPhoneNo1/ToPhoneNo2/ToPhoneNoN/sinch://ServicePlanId:ApiToken@ShortCode/ToPhoneNosinch://ServicePlanId:ApiToken@ShortCode/ToPhoneNo1/ToPhoneNo2/ToPhoneNoN/Twiliotwilio://(TCP) 443twilio://AccountSid:AuthToken@FromPhoneNotwilio://AccountSid:AuthToken@FromPhoneNo/ToPhoneNotwilio://AccountSid:AuthToken@FromPhoneNo/ToPhoneNo1/ToPhoneNo2/ToPhoneNoN/twilio://AccountSid:AuthToken@ShortCode/ToPhoneNotwilio://AccountSid:AuthToken@ShortCode/ToPhoneNo1/ToPhoneNo2/ToPhoneNoN/Desktop Notification SupportNotification ServiceService IDDefault PortExample SyntaxLinux DBus Notificationsdbus://qt://glib://kde://n/adbus://qt://glib://kde://Linux Gnome Notificationsgnome://n/agnome://MacOS X Notificationsmacosx://n/amacosx://Windows Notificationswindows://n/awindows://Email SupportService IDDefault PortExample Syntaxmailto://(TCP) 25mailto://userid:pass@domain.commailto://domain.com?user=userid&pass=passwordmailto://domain.com:2525?user=userid&pass=passwordmailto://user@gmail.com&pass=passwordmailto://mySendingUsername:mySendingPassword@example.com?to=receivingAddress@example.commailto://userid:password@example.com?smtp=mail.example.com&from=noreply@example.com&name=no%20replymailtos://(TCP) 587mailtos://userid:pass@domain.commailtos://domain.com?user=userid&pass=passwordmailtos://domain.com:465?user=userid&pass=passwordmailtos://user@hotmail.com&pass=passwordmailtos://mySendingUsername:mySendingPassword@example.com?to=receivingAddress@example.commailtos://userid:password@example.com?smtp=mail.example.com&from=noreply@example.com&name=no%20replyApprise have some email services built right into it (such as yahoo, fastmail, hotmail, gmail, etc) that greatly simplify the mailto:// service.  See more detailshere.Custom NotificationsPost MethodService IDDefault PortExample SyntaxJSONjson:// or jsons://(TCP) 80 or 443json://hostnamejson://user@hostnamejson://user:password@hostname:portjson://hostname/a/path/to/post/toXMLxml:// or xmls://(TCP) 80 or 443xml://hostnamexml://user@hostnamexml://user:password@hostname:portxml://hostname/a/path/to/post/toInstallationThe easiest way is to install this package is from pypi:pipinstallappriseCommand LineA small command line tool is also provided with this package calledapprise. If you know the server url's you wish to notify, you can simply provide them all on the command line and send your notifications that way:# Send a notification to as many servers as you want# as you can easily chain one after another (the -vv provides some# additional verbosity to help let you know what is going on):apprise-vv-t'my title'-b'my notification body'\'mailto://myemail:mypass@gmail.com'\'pbul://o.gn5kj6nfhv736I7jC3cj3QLRiyhgl98b'# If you don't specify a --body (-b) then stdin is used allowing# you to use the tool as part of your every day administration:cat/proc/cpuinfo|apprise-vv-t'cpu info'\'mailto://myemail:mypass@gmail.com'# The title field is totally optionaluptime|apprise-vv\'discord:///4174216298/JHMHI8qBe7bk2ZwO5U711o3dV_js'Configuration FilesNo one wants to put their credentials out for everyone to see on the command line.  No problemapprisealso supports configuration files.  It can handle both a specificYAML formator a very simpleTEXT format. You can also pull these configuration files via an HTTP query too! You can read more about the expected structure of the configuration fileshere.# By default if no url or configuration is specified aprise will attempt to load# configuration files (if present):#  ~/.apprise#  ~/.apprise.yml#  ~/.config/apprise#  ~/.config/apprise.yml# Windows users can store their default configuration files here:#  %APPDATA%/Apprise/apprise#  %APPDATA%/Apprise/apprise.yml#  %LOCALAPPDATA%/Apprise/apprise#  %LOCALAPPDATA%/Apprise/apprise.yml# If you loaded one of those files, your command line gets really easy:apprise-vv-t'my title'-b'my notification body'# If you want to deviate from the default paths or specify more than one,# just specify them using the --config switch:apprise-vv-t'my title'-b'my notification body'\--config=/path/to/my/config.yml# Got lots of configuration locations? No problem, you can specify them all:# Apprise can even fetch the configuration from over a network!apprise-vv-t'my title'-b'my notification body'\--config=/path/to/my/config.yml\--config=https://localhost/my/apprise/configAttaching FilesApprise also supports file attachments too! Specify as many attachments to a notification as you want.# Send a funny image you found on the internet to a colleague:apprise-vv--title'Agile Joke'\--body'Did you see this one yet?'\--attachhttps://i.redd.it/my2t4d2fx0u31.jpg\'mailto://myemail:mypass@gmail.com'# Easily send an update from a critical server to your dev teamapprise-vv--title'system crash'\--body'I do not think Jim fixed the bug; see attached...'\--attach/var/log/myprogram.log\--attach/var/debug/core.2345\--tagdevteamDevelopersTo send a notification from within your python application, just do the following:importapprise# Create an Apprise instanceapobj=apprise.Apprise()# Add all of the notification services by their server url.# A sample email notification:apobj.add('mailto://myuserid:mypass@gmail.com')# A sample pushbullet notificationapobj.add('pbul://o.gn5kj6nfhv736I7jC3cj3QLRiyhgl98b')# Then notify these services any time you desire. The below would# notify all of the services loaded into our Apprise object.apobj.notify(body='what a great notification service!',title='my notification title',)Configuration FilesDevelopers need access to configuration files too. The good news is their use just involves declaring another object (calledAppriseConfig) that theAppriseobject can ingest.  You can also freely mix and match config and notification entries as often as you wish! You can read more about the expected structure of the configuration fileshere.importapprise# Create an Apprise instanceapobj=apprise.Apprise()# Create an Config instanceconfig=apprise.AppriseConfig()# Add a configuration source:config.add('/path/to/my/config.yml')# Add another...config.add('https://myserver:8080/path/to/config')# Make sure to add our config into our apprise objectapobj.add(config)# You can mix and match; add an entry directly if you want too# In this entry we associate the 'admin' tag with our notificationapobj.add('mailto://myuser:mypass@hotmail.com',tag='admin')# Then notify these services any time you desire. The below would# notify all of the services that have not been bound to any specific# tag.apobj.notify(body='what a great notification service!',title='my notification title',)# Tagging allows you to specifically target only specific notification# services you've loaded:apobj.notify(body='send a notification to our admin group',title='Attention Admins',# notify any services tagged with the 'admin' tagtag='admin',)# If you want to notify absolutely everything (reguardless of whether# it's been tagged or not), just use the reserved tag of 'all':apobj.notify(body='send a notification to our admin group',title='Attention Admins',# notify absolutely everything loaded, reguardless on wether# it has a tag associated with it or not:tag='all',)Attaching FilesAttachments are very easy to send using the Apprise API:importapprise# Create an Apprise instanceapobj=apprise.Apprise()# Add at least one service you want to notifyapobj.add('mailto://myuser:mypass@hotmail.com')# Then send your attachment.apobj.notify(title='A great photo of our family',body='The flash caused Jane to close her eyes! hah! :)',attach='/local/path/to/my/DSC_003.jpg',)# Send a web based attachment too! In the below example, we connect to a home# security camera and send a live image to an email. By default remote web# content is cached but for a security camera, we might want to call notify# again later in our code so we want our last image retrieved to expire(in# this case after 3 seconds).apobj.notify(title='Latest security image',attach='http:/admin:password@hikvision-cam01/ISAPI/Streaming/channels/101/picture?cache=3')To send more than one attachment, just use a list, set, or tuple instead:importapprise# Create an Apprise instanceapobj=apprise.Apprise()# Add at least one service you want to notifyapobj.add('mailto://myuser:mypass@hotmail.com')# Now add all of the entries we're intrested in:attach=(# ?name= allows us to rename the actual jpeg as found on the site# to be another name when sent to our receipient(s)'https://i.redd.it/my2t4d2fx0u31.jpg?name=FlyingToMars.jpg',# Now add another:'/path/to/funny/joke.gif',)# Send your multiple attachments with a single notify call:apobj.notify(title='Some good jokes.',body='Hey guys, check out these!',attach=attach,)Want To Learn More?If you're interested in reading more about this and other methods on how to customize your own notifications, please check out the following links:📣Using the CLI🛠️Development API🔧Troubleshooting⚙️Configuration File Help🌎Apprise API/Web Interface🎉ShowcaseWant to help make Apprise better?💡Contribute to the Apprise Code Base❤️Sponsorship and Donations