Novu API
GET /v1/subscribers/{id}/notifications/feed endpoint removal
Deprecated, no dateSubscribe to Novu APIShare
The GET /v1/subscribers/{id}/notifications/feed endpoint is deprecated without a shutdown date. Calls made to this route will eventually fail as Novu API advises to use v2 API instead. This change impacts requests intended to retrieve subscriber in-app notifications by its unique key identifier.
Calls it hits
GET /v1/subscribers/{id}/notifications/feed
What to use instead of these calls
List in-app notifications with GET /v2/subscribers/{subscriberId}/notifications.
In Novu API's words
This API is deprecated, use v2 API instead. Retrieve subscriber in-app notifications by its unique key identifier
Facts
- API
- Novu API
api.novu.co - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Novu API's own pages
Questions
When does this change take effect?
Novu API deprecated GET /v1/subscribers/{id}/notifications/feed without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Novu API 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 Novu API 5
-
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-allEndpoint 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.