Notify an external apprise server

❓ Question

Context:

I have a standalone apprise container running to manage all my notifications. This is the single place where I want to store my credentials regarding notifications. I created a configuration where I link tags to my notification services. So far this is working great.

Some services (for example uptime-kuma) are embedding apprise as a notification platform where I can use apprise url’s to send notifications.

Problem:

I would like to send uptime-kuma notifications with my external apprise server using the tags and not the embedded one where I have to provide my credentials again.

Question:

Is it possible to include apprise as notification service to apprise so that apprise could forward the request to an external apprise server. For example with an url like apprise://url/key/tag or something?

[svenjochems]

Possible solution to prevent infinite loops:

• generate a random identifier for every apprise instance, at installation or at startup
• append this random identifier as a query param when forwarding the request to another apprise instance
• if apprise receives a request which already contains his own identifier we have a loop => drop request or return error response

Example: Request -> apprise1 -> apprise2 -> apprise3 -> apprise1 input: apprise://input apprise1 output: apprise://input?serverId=appriseid1 apprise2 output: apprise://input?serverId=appriseid1&serverId=appriseId2 apprise3 output: apprise://input?serverId=appriseid1&serverId=appriseId2&serverId=apprise3 apprise1: error because input already contains serverId=appriseid1

This can also be used to track the complete path when load balancing apprise.

[caronc]

That’s actually a really good idea! Let me see what I can do