Config ID: 54fefe0a4b7fc89344e664d32a1eaecb80865cd9ec42d04e48ba33c1ddd87649
Getting Started
  1. Verify your Apprise API Status: autorenew
  2. The following is your Apprise Configuration ID:

    54fefe0a4b7fc89344e664d32a1eaecb80865cd9ec42d04e48ba33c1ddd87649
    For some examples on how to build a development environment around this: click here.

  3. In the future you can return to this configuration screen at any time by placing the following into your browser:
    http://apprise.nuc10.kyiv.ua/cfg/54fefe0a4b7fc89344e664d32a1eaecb80865cd9ec42d04e48ba33c1ddd87649
  4. Use the settings Configuration section to prepare and save your Apprise configuration.
    lightbulb_outlineYou can always refer to the Apprise Wiki if you're having troubles assembling your URL(s).
  5. Use the web Review section to review what was parsed/detected from your defined configuration.
  6. Use the announcement Notifications section to test out your saved configuration.
    lightbulb_outline: The number also provided in the announcement Notifications tab identifies how many notifications will be sent (based on tags/configuration provided) when using this section.
Working Remotely With Your Configuration
Using The Apprise CLI

The following command would cause apprise to directly notify all of your services:

apprise --body="Test Message" \
    apprise://apprise.nuc10.kyiv.ua/54fefe0a4b7fc89344e664d32a1eaecb80865cd9ec42d04e48ba33c1ddd87649/?tags=all
Send one or more attachments like this:
apprise --body="Test Message" \
    apprise://apprise.nuc10.kyiv.ua/54fefe0a4b7fc89344e664d32a1eaecb80865cd9ec42d04e48ba33c1ddd87649/?tags=all \
    --attach=https://raw.githubusercontent.com/caronc/apprise/master/apprise/assets/themes/default/apprise-logo.png
    --attach=/path/to/an/attachment.jpeg \

The following command would cause apprise to retrieve the configuration loaded and send a test notification to all of your added services:

apprise --body="Test Message" --tag=all \
    --config=http://apprise.nuc10.kyiv.ua/cfg/54fefe0a4b7fc89344e664d32a1eaecb80865cd9ec42d04e48ba33c1ddd87649
You may also create an Apprise configuration file that contains this line somewhere in it:
include http://apprise.nuc10.kyiv.ua/cfg/54fefe0a4b7fc89344e664d32a1eaecb80865cd9ec42d04e48ba33c1ddd87649
By leveraging the include directive, it will automatically be referenced for future calls to the apprise tool. All future calls using Apprise now simplify to:
apprise --body="Test Message" --tag=all
Using CURL

The following command would cause the Apprise API to notify all of your services:

curl -X POST \
    -F "body=Test Message" \
    -F "tags=all" \
    http://apprise.nuc10.kyiv.ua/notify/54fefe0a4b7fc89344e664d32a1eaecb80865cd9ec42d04e48ba33c1ddd87649
When sending attachments, curl requires all local files be prefixed with @. You can an add attachment like this:
curl -X POST \
    -F "tags=all" \
    -F "body=Test Message" \
    -F attach=@Screenshot-1.png \
    http://apprise.nuc10.kyiv.ua/notify/54fefe0a4b7fc89344e664d32a1eaecb80865cd9ec42d04e48ba33c1ddd87649
When sending more than one attachment, you must uniquely assign each attachment to a new ID. The example below leverages attach1 and attach2:
curl -X POST \
    -F "tags=all" \
    -F "body=Test Message" \
    -F attach1=@Screenshot-1.png \
    -F attach2=@/my/path/to/Apprise.doc \
    http://apprise.nuc10.kyiv.ua/notify/54fefe0a4b7fc89344e664d32a1eaecb80865cd9ec42d04e48ba33c1ddd87649
Sends a notification to our endpoints with an attachment and no body specified:
curl -X POST \
    -F "tag=all" \
    -F "attach=https://raw.githubusercontent.com/caronc/apprise/master/apprise/assets/themes/default/apprise-logo.png" \
    http://apprise.nuc10.kyiv.ua/notify/54fefe0a4b7fc89344e664d32a1eaecb80865cd9ec42d04e48ba33c1ddd87649

Define your configuration below:

info Once you have successfully loaded at least one Apprise URL on the settings Configuration section, your loaded entries will display here.
Loaded Configuration
Tip: Click on a tag (🏷️) to pre-select it in the announcementNotifications section.
You can send a notification using the loaded configuration:
restore_page