eu.api.novu.co
POST /v1/subscribers/{id}/messages/mark-all endpoint removal
Deprecated, no dateSubscribe to eu.api.novu.coShare
eu.api.novu.co deprecated the POST /v1/subscribers/{id}/messages/mark-all endpoint without a shutdown date. Calls to this route will eventually fail. eu.api.novu.co advises to use v2 API instead to update subscriber in-app notifications state.
Calls it hits
POST /v1/subscribers/{id}/messages/mark-all
What to use instead of these calls
Mark all notifications with POST /v2/subscribers/{subscriberId}/notifications/read, /seen, or /archive instead.
In eu.api.novu.co's words
This API is deprecated, use v2 API instead. Update all subscriber in-app notifications state
Facts
- API
- eu.api.novu.co
eu.api.novu.co - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against eu.api.novu.co's own pages
Questions
When does this change take effect?
eu.api.novu.co deprecated POST /v1/subscribers/{id}/messages/mark-all without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: eu.api.novu.co has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from eu.api.novu.co 5
-
No date
GET /v1/subscribers/{id}/notifications/feedEndpoint removal Deprecated, no date -
No date
GET /v1/subscribers/{id}/notifications/unseenEndpoint removal Deprecated, no date -
No date
POST /v1/integrations/chat/oauthEndpoint removal Deprecated, no date -
No date
POST /v1/subscribers/{id}/messages/{id}/actions/{id}Endpoint removal Deprecated, no date -
No date
POST /v1/subscribers/{id}/messages/mark-asEndpoint removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.