/api/1.0/webhook → version retirement
Revolut Business API
Deprecated, no date
Revolut Business API has deprecated version 1 of the Webhooks API without announcing a shutdown date. The deprecation applies to calls targeting the /api/1.0/webhook endpoint, which are slated to fail. The provider notes that this version is deprecated.
Calls it hits
/api/1.0/webhook
What to use instead of these calls
Manage webhooks using the Webhooks API v2 instead. Update your integration to use POST /api/2.0/webhooks, GET /api/2.0/webhooks, and DELETE /api/2.0/webhooks/{webhook_id}.
In Revolut Business API's words
This is the v1 of the Webhooks API. This version is deprecated.
Facts
- API
- Revolut Business API
b2b.revolut.com - Kind
- Version retirement
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Revolut Business API's own pages
Questions
When does this change take effect?
Revolut Business API deprecated /api/1.0/webhook without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Revolut Business 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 Revolut Business API 1
-
No date
GET /api/1.0/transaction/{}Endpoint 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.