Skip to content

Using an actual apprise URL with a tag (POST) within ChangeDetection.io notification #2096

@voc0der

Description

@voc0der

Trying to use an Apprise-API REST POST endpoint/url or similar to accomplish sending notifications.

Is this documented anywhere? I'm trying to basically do:

curl -X POST \
-F "body=This is a test!" \
-F "tag=discord_backup" \
http://apprise-api:8000/notify/apprise

But the changedetection.io version. Which ironically, and confusingly, is the same as apprise-urls. Love the feature, but I didn't get it until I read it a few times.

In the documentation it seems to suggest writing the full discord URL with webhook+token, or signal call with sensitive info, but that goes against the whole point of what apprise-api config does. I've tested that, and it does work, but it has that caveat about not using apprise-api for what it's designed to do.

What is the best way to do this? I'm probably being stupid and overlooking something obvious.

No version of:

post://apprise-api:8000/notify/apprise?+tag=discord_backup

When I click notification history, it just goes like:

2024/01/10 16:36:14,000 - SENDING - [{"title": "Test", "body": "hee", "url": "post://apprise-api:8000/notify/apprise?+tag=discord_backup", "body_format": "Text"}]
2024/01/10 16:09:28,000 - SENDING - [{"title": "Test", "body": "hee", "url": "post://apprise-api:8000/notify/apprise?+tag=discord_backup&+title=xyz&+body=yzxx", "body_format": "Text"}]
2024/01/10 16:08:25,000 - SENDING - [{"title": "Test", "body": "hee", "url": "post://apprise-api:8000/notify/apprise?tag=discord_backup&title=xyz&body=yzxx", "body_format": "Text"}]
2024/01/10 16:07:59,000 - SENDING - [{"title": "Test", "body": "hee", "url": "post://apprise-api:8000/notify/apprise?tag=discord_backup", "body_format": "Text"}]

In apprise-api logs...

2024-01-10 10:46:12,253 [WARNING] django.request: Bad Request: /notify/apprise
[pid: 147|app: 0|req: 462/598] 172.28.0.110 () {30 vars in 388 bytes} [Wed Jan 10 10:46:12 2024] POST /notify/apprise => generated 36 bytes in 2 msecs (HTTP/1.1 400) 5 headers in 291 bytes (1 switches on core 0)

Seems to work for me, although of course the curl command up top works fine when docker exec -it apprise-api bash.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions