Notifyre Notifications

Account Setup
Section titled “Account Setup”- Sign up at notifyre.com and log in.
- Navigate to Settings > Developer.
- Click New to create an API token and copy it — it is only shown once.
Notifyre supports both SMS delivery and fax delivery from the same API key. Fax mode is activated by adding ?mode=fax to the Apprise URL. Attachments (PDF, DOCX, PNG, JPEG, TIFF, and more) are supported in fax mode and are base64-encoded as fax document pages. The notification body is always included as a plain-text cover page prepended before any file attachments.
Syntax
Section titled “Syntax”Valid syntax is as follows:
notifyre://{apikey}/{phoneno}notifyre://{apikey}/{phoneno1}/{phoneno2}notifyre://{apikey}/{phoneno}?from={from}notifyre://{apikey}/{phoneno}?campaign={campaign}notifyre://{apikey}/{faxno}?mode=faxnotifyre://{apikey}/{faxno}?mode=fax&from={from}notifyre://{apikey}/{faxno}?mode=fax&template={template}notifyre://{apikey}/{faxno}?mode=fax&hq=nonotifyre://{apikey}/{faxno}?mode=fax&ref={ref}notifyre://{apikey}/{faxno}?mode=fax&header={header}notifyre://{apikey}/{faxno1}/{faxno2}?mode=fax
Parameter Breakdown
Section titled “Parameter Breakdown”| Variable | Required | Description |
|---|---|---|
| apikey | *Yes | Your Notifyre API token (Settings > Developer). |
| phoneno | *Yes | The target phone or fax number to notify. Numbers must include the country code (e.g. +15551234567). |
| from | No | The sender phone or fax number. When omitted, Notifyre uses a shared number from your account pool. |
| mode | No | Delivery mode: sms (default) or fax. |
| campaign | No | Campaign name attached to the message. Defaults to the Apprise application ID (Apprise). Applies to both SMS and fax. |
| template | No | Fax template name. Used only in fax mode. |
| ref | No | Client reference string for tracking. Used only in fax mode. |
| hq | No | High-quality fax flag. Set to no to disable. Defaults to yes. Used only in fax mode. |
| header | No | Cover page header text. Used only in fax mode. |
Global Parameters
Section titled “Global Parameters”| Variable | Description |
|---|---|
| overflow | This 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. |
| format | This 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. |
| verify | External 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. |
| redirect | By default, Apprise will follow HTTP redirects (3xx responses) issued by the remote server, matching the behaviour of the underlying requests library. If you want to prevent custom headers and credentials from being forwarded to destinations that differ from the original URL, set this to no. By default it is set to yes. |
| cto | This 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. |
| rto | This 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. |
| emojis | Enable 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. |
| tz | Identify 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. |
| retry | The number of additional delivery attempts to make after the first failure before giving up. Accepts an integer in the range 0 to 10. The default is 0 (no retries — a single attempt is made). When combined with wait, Apprise pauses the specified number of seconds between each attempt. |
| wait | The number of seconds to pause between retry attempts. Accepts a decimal value in the range 0.0 to 20.0; integer values are promoted to float automatically. The default is 0.5. This value is only meaningful when retry is greater than zero — a service with retry=0 makes exactly one attempt regardless of the wait value. |
| optional | When set to yes, a delivery failure for this service is silently absorbed. The overall notify() call still returns True even if this endpoint was unreachable, provided that every required (non-optional) service in the same batch succeeded. Setting this flag does not skip delivery or bypass retry logic — all configured retry attempts are still made before the failure is absorbed. By default this is set to no, meaning every failure is propagated to the caller. |
Examples
Section titled “Examples”Send an SMS to a single number:
apprise -vv -t "Alert" -b "Server is down" \ "notifyre://YOURAPIKEY/+15551234567"Send an SMS to multiple numbers:
apprise -vv -t "Alert" -b "Server is down" \ "notifyre://YOURAPIKEY/+15551234567/+15559876543"Send a fax with the notification body as cover sheet text:
apprise -vv -t "Notice" -b "Please review the attached document." \ "notifyre://YOURAPIKEY/+15551234567?mode=fax"Send a fax with a PDF attachment:
apprise -vv -t "Invoice" -b "Please find the invoice attached." \ --attach /path/to/invoice.pdf \ "notifyre://YOURAPIKEY/+15551234567?mode=fax"Send a fax specifying the sender number:
apprise -vv -t "Notice" -b "Document enclosed." \ "notifyre://YOURAPIKEY/+15551234567?mode=fax&from=+15550000001" Questions or Feedback?
Technical Issues
Having trouble with the code? Open an issue on GitHub:
Made with love from Canada