Push notifications API

The push API lets you send notifications from your own systems (CRM, ERP, marketing automation) without going through the backoffice. It is currently the only documented public Reskyt API.

Authentication

Header	Value	Required
`Content-Type`	`application/json`	Yes
`x-api-key`	Your API key	Yes

API keys are generated from the Reskyt panel.

Endpoint

POST https://push.api.reskyt.com/push/send

Payload

{
  "title": "Your order is on its way",
  "heading": "Shipping",
  "dateEnd": 1790000000,
  "url": "https://yourstore.com/offers",
  "pictureUrl": "https://yourstore.com/img/preview.jpg",
  "utmCampaign": "black_friday_2026",
  "deviceId": [
    "41dc840f7e76bcec71a40bce87699431",
    "076b3c207b9a010d654efdfab92cb898"
  ]
}

Fields

Field	Type	Required	Description
`title`	string	Yes	Text or body of the notification.
`heading`	string	No	Title of the notification.
`deviceId`	string[]	Yes in V2	Recipients of the send, identified by their hashed installation ID.
`dateEnd`	number	No	Unix timestamp in seconds at which the notification expires. If not specified, the API applies 7 days from the send.
`url`	string	No	URL opened when the notification is tapped.
`pictureUrl`	string	No	URL of the preview image.
`utmCampaign`	string	No	Campaign identifier or label.
`tokens`	string[]	V1 only	Recipients identified by their MD5 push token. Only for customers coming from V1; V2 uses `deviceId`.

deviceId carries hashed installation IDs, not APNs or FCM tokens. The recommended flow to obtain them is:

Check that the user agent contains rktwebview, which is what indicates that the code is running inside the app. See detecting that you are inside the app.
During login or sign-up, call window.ReskytLayout.device.getId(), which returns a promise.
Store the returned hashed installation ID.
Associate it with the corresponding user in your systems.
Then use it as the value of deviceId in your sends.

Without step 4 it is not possible to segment by customer.

Migrating from V1

If you already send notifications with V1, you can keep doing so with the tokens you have stored, in tokens.

To move to V2, start storing each device’s hashed installation ID, following the flow above, the same way you stored the tokens, and send it in deviceId. Push tokens can change over time, while the hashed installation ID stays the same for as long as the app remains installed.

Example

curl -X POST https://push.api.reskyt.com/push/send \
  -H "Content-Type: application/json" \
  -H "x-api-key: $RESKYT_API_KEY" \
  -d '{
    "title": "Your order is on its way",
    "heading": "Shipping",
    "dateEnd": 1790000000,
    "url": "https://yourstore.com/orders/1234",
    "deviceId": ["41dc840f7e76bcec71a40bce87699431"]
  }'