Okapi Okapi
Add to GitHub

GET /api/1.0/transaction/{} → endpoint removal

Revolut Business API

Deprecated, no date

The provider deprecated the query parameter id_type on the GET /api/1.0/transaction/{} endpoint without a shutdown date. The field will be removed in a future release, after which affected requests fail. Calls using this parameter will need to be updated before its removal.

Calls it hits

  • GET /api/1.0/transaction/{}
  • query parameter id_type

What to use instead of these calls

Retrieve transactions by request ID with GET /api/1.0/transactions instead of id_type=request_id.

In Revolut Business API's words

This field is now deprecated and will be removed in a future release.

Revolut Business API, Announcement

Facts

API
Revolut Business API b2b.revolut.com
Kind
Endpoint removal
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 GET /api/1.0/transaction/{}, query parameter id_type 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

  1. No date /api/1.0/webhookVersion retirement 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