October 26, 2026
· 3 min read
This release introduces comprehensive push notification management capabilities to the API, allowing developers to retrieve, mark as read, and delete push notifications. Additionally, customer notification preferences have been extended to include push notification settings, giving users granular control over how they receive notifications.
- GET /customers/{id}/notification_preferences – Retrieve customer notification preferences, now including a
push_enabledflag to determine whether push notifications are enabled for the customer. - PATCH /customers/{id}/notification_preferences/{notification_preference_id} – Update customer notification preferences with the ability to enable or disable push notifications via the new
push_enabledfield. - GET /push_notifications – Retrieve a list of push notifications for the authenticated user.
- POST /push_notifications/mark_all_read – Mark all push notifications as read in a single operation.
- DELETE /push_notifications/{id} – Delete a specific push notification.
- POST /push_notifications/{id}/mark_read – Mark a specific push notification as read.
GET /customers/{id}/notification_preferences
- the response property
idbecame nullable for the status200(media type: application/json) - added the optional property
push_enabledto the response with the200status (media type: application/json)
PATCH /customers/{id}/notification_preferences/{notification_preference_id}
- the response property
idbecame nullable for the status200(media type: application/json) - added the new optional request property
push_enabled(media type: application/json) - removed the pattern
^\d+$from thepathrequest parameternotification_preference_id - added the optional property
push_enabledto the response with the200status (media type: application/json)
GET /push_notifications
- endpoint added
POST /push_notifications/mark_all_read
- endpoint added
DELETE /push_notifications/{id}
- endpoint added
POST /push_notifications/{id}/mark_read
- endpoint added