logo EZ Notification Forwarder
Developed by matas consulting 		[en] [de]
[Overview] [Screenshots] [Download] [Documentation] [Support] [Privacy] [Imprint]

Documentation

Settings json examples

Notification Body json examples

Target URL

Syntax
  • http[s]://servername[:port][/path[?parms]]
Example (without path and without parameters)
  • http://acme.com/toasts
Using variables
In general, all elements available in notification body json can be used as 'variables' within target URLs. Just insert casesensitiv variable name with preceeding dollar sign ('$') at any place within URL.

Example (with some of the available variables as parameter)
  • http://acme.com/toasts?t=$Title&c=$Content&h=$Host
Example with 'UserProperties'
Assuming, your configuration settings json contains below 'UserProperties' element:
<...>
"UserProperties": [
  { "Name": "Foo", "Value": "Doo" } ,
  { "Name": "Woo", "Value": "Zoo" } ]
<...>
Than those properties can be used within target URLs the same way like variables from notification body json. Just insert the property name with preceeding dollar sign ('$') at any place within target URLs. On target invocation, the name token will be replaced with corresponding value from configuration setting.

Example (with 'UserProperties' names)
  • http://acme.com/toasts?t=$Title&c=$Content&h=$Host&p1=$Foo&p2=$Woo

Notes

  • Due to limitiations within the UWP framework, notifications can not be forwarded to "localhost".

  • Some RESTful APIs like for example -->< notifymydevice.com > called with query parameters in URL require to use http method GET instead of POST in order to accept and process the request correctly.

[top]

[Overview] [Screenshots] [Download] [Documentation] [Support] [Privacy] [Imprint]
Last update 2024/03/07 00:30