Need an API Key? Get up to 10.000 requests per day for free!


Introduction is a service that allows you to set up precisely timed and highly customizable HTTP requests.
There are many use cases such as delegating important HTTP calls to the cloud, setting up reoccuring events such as monthly payments etc.
or simply delaying a request for various reasons.
To create, update or delete notifications we offer a full blown dashboard, a RESTful API and several SDK's to make your life easier.


When setting up a one time or reoccuring task, we call the task itself a notification.
A notification is defined by its following properties:

Since a notification may have an interval and end time, it may generate multiple HTTP requests. We refer to these as requests. Notifications without an interval and end time generate only one request immediatly or at the specified start time.


We use the term request to describe each HTTP request generated by a notification.
A request will contain some default and any custom headers you define in the notification.
It will also, if set, have the custom body defined by the notification.
Requests of a notification with a body but without a custom method will default to POST, others to GET.


Every request generated will be made at the notifications URL.
To prevent users from spamming third party endpoints we require you to verify that you own the domain you provide in the URL.
We will perform this validation process once every week to ensure that users only target their currently owned servers.
Be sure to include the correct http or https protocol as well as any ports if required by the endpoint.


You may set up as many custom headers as you like.
This is especially useful for authentication purposes.


You can use the body property to set up your desired payload for each request.
The body must be defined as a JSON object/string/number.
When providing a JSON object each request will have it as the body.
However when provided with a string or a number, the body will look as follows:

{ "number": 12390123 }  or  { "string": "a string as body property" }


The HTTP method with which requests will be made with.
Attention: We do not validate your provided method. Any type of string will be accepted so be sure to double check.


The time at which the first request will take place.
When providing a start time without an interval and end time, the notification will generate only a single request at the specified time.
Like all times, the start time is set in UTC - millieseconds.


The interval in which requests will be generated.
If you set an interval, you must also set an end time.
When ommitting the start time, requests will be generated once the given interval passed once from now on. Use either a number to specify a constant interval of millieseconds or a string to specify date like intervals.
You can choose between following date like interval types:


When using a number as the interval property, requests will be generated in a constant interval up until the end time (included). The minimum is 1 second.

10000      /* Every 10 seconds */


The 'DAILY' type requires only one argument, the time at which requests shall be sent daily.

"DAILY 12:00:20"      /* Every day at 12:00:20 o'clock */


The 'WEEKLY' type requires the day of the week and the time at which the requests shall be sent.

"WEEKLY 7 23:59:59"      /* Every week on sunday at 23:59:59 o'clock */


The 'MONTHLY' type requires the day of the month as well as the time of day.

"MONTHLY 28 10:00:00"      /* Each month on the 28th at 10 o'clock */


The 'YEARLY' type requires a month, day and time argument.

"YEARLY 12 28 23:12:23"      /* Every year in december, on the 28th at 23:12:23 o'clock */


If set, the last notification request will be sent at or before this time, depending on the set interval.
No request will ever be made later than the end time.
Like all times, the end time is set in UTC - millieseconds.


Certain notifications might be very important and may not fail, even if your server is offline for a short period of time.
With the retry property you make sure that each request is retried until it either succeeds or a specific count of retries is hit.
For this you specify a retry count as well as an interval in which the request will be retried.

    "interval": 3600,      /* retry once every minute */
    "count": 3      /* dismiss request if failed more than 3 times */    

Was this helpful?

back to top

Thank you!

Your feedback is our most valuable source for product improvements.
We are very happy that you are taking the time to tell us your thoughts!
This is completely anonymous.