Important: If you are unable to resolve your developer-related question via our public Help Center articles, please visit the Developer Dashboard here. Within the developer dashboard, you will be able to submit a support ticket that will be answered by our dedicated team.
Timeline
- Announcement Date: 2021/07/29
- Release Date: 2021/08/10
Description
Impacted actions
What has changed?
The nonce parameter is now mandatory.
Please refer below to get more information.
Sequence for query parameters
Two sequences can be used to call the service Notify.subscribe.
Sequence 1
This sequence should be used to subscribe to the Data API notifications. You will be notified on your callback URL when a new data is available for a specific user. You need to subscribe for each individual user.
Query parameters
- action [required]
- callbackurl[required]
- appli [required]
Header parameters
- Authorization Bearer {access_token}
Sequence 2
This sequence should be used to subscribe to the Advanced User and SDK API notifications. You will be notified on your callback URL depending on various events relating to your users and devices management. You need to subscribe once per developer application.
Query parameters
- action [required]
- callbackurl[required]
- appli [required]
- client_id [required]
- nonce [required]
- signature [required]
Header parameters
none
Am I impacted?
- You are impacted if you were using the sequence 2 without the nonce parameter.
Please note that you are not impacted if you use this service for the Data API notifications using an access_token in the Authorization header.
How can I switch from the previous endpoint?
When using the sequence 2, you must add the nonce parameter and follow the provided instructions to build a valid signature.