eu.api.novu.co
POST /v1/subscribers/{id}/messages/{id}/actions/{id} endpoint removal
Deprecated, no dateSubscribe to eu.api.novu.coShare
The endpoint POST /v1/subscribers/{id}/messages/{id}/actions/{id} is deprecated without a shutdown date, and calls to it will fail. The deprecation applies to operations used to update an in-app notification action status.
Calls it hits
POST /v1/subscribers/{id}/messages/{id}/actions/{id}
What to use instead of these calls
Complete or revert an action using PATCH /v2/subscribers/{subscriberId}/notifications/{notificationId}/actions/{actionType}/complete or /revert instead.
In eu.api.novu.co's words
This API is deprecated, use v2 API instead. Update in-app notification's action status
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/{id}/actions/{id} 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/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.