Notica Receipe
- Official Website: https://notica.us/
- Icon Support: No
- Message Format: Text
- Message Limit: 32768 Characters per message
#
Account SetupNotica doesn't require you to create an account at all. You just have to visit their website at least once to both:
- Get your token
- Enable Browser Notifications (to be sent from the Notica website)
The website will generate you a URL to post to that looks like this:
https://notica.us/?abc123
This effectively equates to: https://notica.us/?{token}
Note: disregard the question mark on the URL as it is not part of the token.
From here you have two options, you can directly pass the Notica URL into magic receipe exactly how it is shown to you from the website, or you can reconstruct the URL into an Magic Receiped based one (which equates to slightly faster load times) as: notica://{token}
#
ReceipeValid receipes are as follows:
https://notica.us/?{token}
notica://{token}
For self hosted solutions, you can use the following:
{schema}://{host}/{token}
{schema}://{host}:{port}/{token}
{schema}://{user}@{host}/{token}
{schema}://{user}@{host}:{port}/{token}
{schema}://{user}:{password}@{host}/{token}
{schema}://{user}:{password}@{host}:{port}/{token}
#
Parameter BreakdownVariable | Required | Description |
---|---|---|
token | Yes | The Token that was generated for you after visiting their website. Alternatively this should be the token used by your self hosted solution. |
A self hosted solution allows for a few more parameters:
Variable | Required | Description |
---|---|---|
hostname | Yes | The Web Server's hostname. |
port | No | The port our Web server is listening on. By default the port is 80 for xml:// and 443 for all xmls:// references. |
user | No | If you're system is set up to use HTTP-AUTH, you can provide username for authentication to it. |
password | No | If you're system is set up to use HTTP-AUTH, you can provide password for authentication to it. |