onesignal.com · CommunicationSubscribeShare
Onesignal breaking changes
The breaking changes Onesignal announced that Okapi tracks: 5 in all.
Do you run the Onesignal API? Make sure your users call it right →
At a glance
- API host
onesignal.com- Kind
- Communication
- Versions with breaking changes
- v1 (5)
- Breaking changes tracked
- 5 breaking changes with no date yet
- Last updated
Deprecated, no date yet 5
-
No date
/api/v1/apps/{id}/users/{id}Endpoint removal Deprecated, no date -
No date
GET /api/v1/playersEndpoint removal Deprecated, no date -
No date
GET /api/v1/players/{id}Endpoint removal Deprecated, no date -
No date
POST /api/v1/playersEndpoint removal Deprecated, no date -
No date
PUT /api/v1/players/{id}Endpoint removal Deprecated, no date
Where Okapi reads it
- OpenAPI spec raw.githubusercontent.com/OneSignal/api/main/api.json
- Announcement documentation.onesignal.com/reference/add-a-device
- Announcement documentation.onesignal.com/reference/edit-device
- Announcement documentation.onesignal.com/reference/edit-tags-with-external-user-id
- Announcement documentation.onesignal.com/reference/view-device
- Announcement documentation.onesignal.com/reference/view-devices
Know before your API calls break.
Okapi finds the calls a breaking change hits in your code and opens the pull request that fixes them.
Add to GitHub