Okapi Okapi
Add to GitHub

eu.api.novu.co GET /v1/subscribers/{}/notifications/feed endpoint removal

Deprecated, no date

eu.api.novu.co deprecated GET /v1/subscribers/{}/notifications/feed without giving a shutdown date yet.

Calls it hits

  • GET /v1/subscribers/{}/notifications/feed

What to use instead of these calls

List in-app notifications with GET /v2/subscribers/{subscriberId}/notifications.

In eu.api.novu.co's words

This API is deprecated, use v2 API instead. Retrieve subscriber in-app notifications by its unique key identifier

eu.api.novu.co, Announcement

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 GET /v1/subscribers/{}/notifications/feed 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

  1. No date GET /v1/subscribers/{}/notifications/unseenEndpoint removal Deprecated, no date
  2. No date POST /v1/integrations/chat/oauthEndpoint removal Deprecated, no date
  3. No date POST /v1/subscribers/{}/messages/{}/actions/{}Endpoint removal Deprecated, no date
  4. No date POST /v1/subscribers/{}/messages/mark-allEndpoint removal Deprecated, no date
  5. No date POST /v1/subscribers/{}/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.

Add to GitHub