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

[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.

[voc0der]

Further into this, I cannot seem to make this work.

First tried to make apprise url talk to the host.

apprise://apprise-api:8000/notify?tags=discord_backup

No success.

Then I tried using the key api: https://github.com/caronc/apprise-api#persistent-storage-solution , no luck there either.

Working with key:

curl -X POST -F "body=HELLO" http://apprise-api:8000/notify/7a415742525gere2e8bf8c4361e9777d92f2dfad2359bbd8c9fbcd49

Not working:

post://apprise-api:8000/notify/7a415742525gere2e8bf8c4361e9777d92f2dfad2359bbd8c9fbcd49
form://apprise-api:8000/notify/7a415742525gere2e8bf8c4361e9777d92f2dfad2359bbd8c9fbcd49

Tried adding tags. That doesn't work either.

Tried adding body as a GET parameter in that link. Nope.

If I had to guess it looks like the body tag might just not be getting put in the POST, and thus, it's posting nothing to that.

Then getting HTTP: 204.

There has to be some way to do this.

Edit:

This works. But it's pretty hacky.

form://apprise-api:8000/notify/7a415742525gere2e8bf8c4361e9777d92f2dfad2359bbd8c9fbcd49?:body=Hello

[dgtlmoon]

So its good to start from the start, what version are you running exactly? it is in the issue template that you should tell us :)

what is the goal of your notification? 204 is totally normal if your endpoint returns no text

form:// is for HTTP/HTML/

style form submission, so i'm assuming thats not what you want

check out the bottom half of this tutorial, does it help?

https://changedetection.io/tutorial/automatically-adding-new-pages-watch-existing-results

it atleast worked for me when i was writing the tutorial, and it is tested with the automated tests

changedetection.io/changedetectionio/tests/test_notification.py

Line 285 in 8be0029

test_notification_url = url_for('test_notification_endpoint', _external=True).replace('http://', 'post://')+"?xxx={{ watch_url }}&+custom-header=123"

[dgtlmoon]

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.

post:// and posts:// is not listed here https://github.com/caronc/apprise/ ?

[voc0der]

Apologies for not following the format. Probably came about when I hit custom template because I was confused about what kind of issue this was.

changedetection.io v0.45.12 version.

• The goal is to be able to use an apprise-api service that has been registered as a key, or given a tag. Calling upon apprise-api to execute this. It claims it supports recursive calls.

For example - assigning a tag to services (signal_alert,discord_backup) in apprise-api configuration with yaml.

urls:
  - "signal://signal-cli-rest-api:8080/+1111111111111":
    - to: "group.1111111111111111111111111111111111111111111111111="
      tag: signal_alert
      rto: 30
  - "discord://11111111111/J234234m23jon4IMFEIEWiofwejiofwejouiwe232342342":
    - tag: discord_backup

For example - creating a key in apprise-api with curl for the somekey service. (Assuming apprise-api baseurl is https://notify.some-server.home)

curl -X POST \
-F "urls=signal://signal-cli-rest-api:8080/+111111111111/group.e11111111111111111111111111111111111XMD0=?rto=30" \
https://notify.some-server.home/add/somekey

This key then can be invoked like so (using this REST endpoint https://github.com/caronc/apprise-api#persistent-storage-solution)

curl -X POST \
-F "body=This works" \
https://notify.some-server.home/notify/somekey

post:// is something that is specific to changedetection.io. Unfortunately that doesn't seem to work no matter what I do with it. I'm just throwing the kitchen sink at this at this point.

Given the examples above, I'd expect to be able to invoke somekey, signal_alert, discord_backup somehow. apprise-api does also do webhooks and you can pass Content-Type=application/json and although it might add the header, it's probably still passing the fields in an unexpected structure, or something since it's simply not working like that.

Thank you for your reply!

[voc0der]

After going through and configuring other apps with notifications for apprise-api I realized the problem here. Basically in order for it to easily work as a webhook, if changedetection allowed JSON payload (for example, as another option after text, or markdown for notification style type) and allowed or sent the content-type header, it would work.

Food for thought.