Novu API
POST /v1/integrations/chat/oauth endpoint removal
Deprecated, no dateSubscribe to Novu APIShare
Novu has deprecated the POST /v1/integrations/chat/oauth endpoint without a shutdown date. Calls made to this route are subject to removal and will fail. This change affects any integration workflows relying on the legacy chat OAuth endpoint.
Calls it hits
POST /v1/integrations/chat/oauth
What to use instead of these calls
Generate the OAuth URL with POST /v1/integrations/channel-connections/oauth for connect workflows, or use POST /v1/integrations/channel-endpoints/oauth to link a user.
In Novu API's words
**Deprecated** — use `POST /integrations/channel-connections/oauth` (connect) or `POST /integrations/channel-endpoints/oauth` (link_user) instead.
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 POST /v1/integrations/chat/oauth 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/feedEndpoint removal Deprecated, no date -
No date
GET /v1/subscribers/{id}/notifications/unseenEndpoint 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.