Aller au contenu

Kavenegar Notifications

Ce contenu n’est pas encore disponible dans votre langue.

Overview

To use Kavenegar, first register an account on their website. After you’ve done so, you can get your API Key from the account profile section.

Valid syntax is as follows:

  • kavenegar://{apikey}/{to_phone_no}
  • kavenegar://{from_phone_no}@{apikey}/{to_phone_no}
  • kavenegar://{apikey}/{to_phone_no}/{to_phone_no2}/{to_phone_noN}/
  • kavenegar://{from_phone_no}@{apikey}/{to_phone_no}/{to_phone_no2}/{to_phone_noN}/
VariableRequiredDescription
ApiKeyYesThe API Key associated with your Kavengar account. This is available to you via the account profile section of their website (after logging in).
ToPhoneNoYesKavengar does not handle the + in front of the country codes. You need to substitute the correct amount of zero’s in front of the outbound number in order for the call to be completed.
FromPhoneNoNoThe number you wish to identify your call is coming from. This argument is optional.
VariableDescription
overflowThis parameter can be set to either split, truncate, or upstream. This determines how Apprise delivers the message you pass it. By default this is set to upstream
👉 upstream: Do nothing at all; pass the message exactly as you received it to the service.
👉 truncate: Ensure that the message will fit within the service’s documented upstream message limit. If more information was passed then the defined limit, the overhead information is truncated.
👉 split: similar to truncate except if the message doesn’t fit within the service’s documented upstream message limit, it is split into smaller chunks and they are all delivered sequentially there-after.
formatThis parameter can be set to either text, html, or markdown. Some services support the ability to post content by several different means. The default of this varies (it can be one of the 3 mentioned at any time depending on which service you choose). You can optionally force this setting to stray from the defaults if you wish. If the service doesn’t support different types of transmission formats, then this field is ignored.
verifyExternal requests made to secure locations (such as through the use of https) will have certificates associated with them. By default, Apprise will verify that these certificates are valid; if they are not then no notification will be sent to the source. In some occasions, a user might not have a certificate authority to verify the key against or they trust the source; in this case you will want to set this flag to no. By default it is set to yes.
ctoThis stands for Socket Connect Timeout. This is the number of seconds Requests will wait for your client to establish a connection to a remote machine (corresponding to the connect()) call on the socket. The default value is 4.0 seconds.
rtoThis stands for Socket Read Timeout. This is the number of seconds the client will wait for the server to send a response. The default value is 4.0 seconds.
emojisEnable Emoji support (such as providing :+1: would translate to 👍). By default this is set to no.
Note: Depending on server side settings, the administrator has the power to disable emoji support at a global level; but default this is not the case.
tzIdentify the IANA Time Zone Database you wish to operate as. By default this is detected based on the configuration the server hosting Apprise is running on. You can set this to things like America/Toronto, or any other properly formated Timezone describing your area.

Send a Kavenegar Notification as an SMS:

Terminal window
# Assuming our {ApiKey} is gank339l7jk3cjaE
# Assuming our {PhoneNo} - is in the US somewhere making our country code 001
# - identifies as 800-555-1223
apprise -vv -t "Test Message Title" -b "Test Message Body" \
kavenegar://gank339l7jk3cjaE/0018005551223
# the following would also have worked (spaces, brackets,
# dashes are accepted in a phone no field):
apprise -vv -t "Test Message Title" -b "Test Message Body" \
kavenegar://gank339l7jk3cjaE/001 - (800) 555-1223