Allow sending custom properties in POSTed JSON about ntfy HOT 9 OPEN

What would be the goal of this? Why not just send a custom JSON string as the body of the notification?

from ntfy.

The ntfy server currently only understands predefined properties in the POSTed JSON. Added custom properties do not get forwarded to the frontend. Use case is for self-hosted nfty servers with a custom frontend that needs fields beyond the known message, title etc.

This is the relevant discussion with @binwiederhier .

from ntfy.

I understand what you're asking for (and I agree with binwiederhier that it'd probably be easy to implement), but I don't understand why sending an (escaped) JSON string as the body of the message doesn't work. If you're already building a custom frontend, then you don't need to use any of ntfy's existing fields (except to get your JSON string out).

The current ntfy response looks like this:

{ 
   "id":"fajyTv5FQ0iM",
   "time":1690985276,
   "expires":1691028476,
   "event":"message",
   "topic":"test",
   "message":"testing"
}

You want to change it to this:

{ 
   "id":"fajyTv5FQ0iM",
   "time":1690985276,
   "expires":1691028476,
   "event":"message",
   "topic":"test",
   "message":"testing"
    "extras": {
        "customField": "value"
    }
}

Then, after data = resp.json(), you could access the custom value at data.extras.customField

Why not do this?

{ 
   "id":"fajyTv5FQ0iM",
   "time":1690985276,
   "expires":1691028476,
   "event":"message",
   "topic":"test",
   "message":"\"{\"message\": \"testing\", \"customField\": \"value\"}\""
}

Then, after data = resp.json().message.json(), you could access the custom value at data.customField, right?

from ntfy.

Just opened the issue because as @binwiederhier suggested
(a) this was something he had already considered doing before and
(b) the implementation is easy

Yes, what you propose would work. I'm not saying it wouldn't.
But cannibalizing the preexisting message that has very specific semantics, is a hackey workaround.

from ntfy.

Got it. I hope you don't feel like I am dismissing the value of your proposal. I know other people have already been sending JSON strings with custom fields as the message, so I wanted to make sure you weren't having problems with that.

And I'm sure they will also be happy to have a convenient extras field where they can put additional information instead.

I will see if I can implement this sometime this week.

from ntfy.

I don't feel like that at all. I completely understand you asking for justification esp. when it comes to feature requests. After all it is I who makes a request for your time and effort.

Much appreciated regardless of whether you go ahead with its implementation or not.

from ntfy.

@wunter8 I see the fix. Would it be possible to also get arrays to be allowed values inside the extras object?

from ntfy.

Any update on this?

from ntfy.

Nope. Sorry. I've been busy with work and haven't been able to finish the Android side of things yet

from ntfy.