How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Revolut Payouts API

Endpoints for retrieving information about payouts, allowing merchants to access details of funds withdrawn from their Merchant account to external bank accounts.Merchants can use these endpoints to retrieve a list of payouts and specific payout details. The payout IDs obtained can be used to [generate detailed reports](https://developer.revolut.com/docs/api/merchant#tag-report-runs) that provide comprehensive breakdowns of all transactions contributing to the payout amounts.Payout information, including IDs, can be retrieved via the [Retrieve payout list](https://developer.revolut.com/docs/api/merchant#retrieve-payout-list) endpoint or from [webhook events related to payouts](https://developer.revolut.com/docs/api/merchant#create-webhook#callbacks).

Revolut Payouts API is one of 46 APIs that Revolut publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Payouts. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 2 operations across 2 paths, and defines 7 schemas. It is described by OpenAPI 3.2.0, at version 2026-04-20.

Requests are made against 2 base URLs: https://merchant.revolut.com, https://sandbox-merchant.revolut.com.

2 operations 2 paths 7 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2026-04-20
Base URL
https://b2b.revolut.com/api/1.0
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Revolut Payouts API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (Api-Key). By default, every request must be authenticated.

  • Api-Key — Each Merchant API request must contain an authorization header in the following format: 'Authorization: Bearer ' To use this API, you need to generate API keys…

Paths & Operations 2

Across 2 paths, the API surfaces 2 operations — 2 GET. Each is listed below with its method, path, parameters, and response codes.

Payouts 2

Endpoints for retrieving information about payouts, allowing merchants to access details of funds withdrawn from their Merchant account to external bank accounts. Merchants can us…

GET
/api/payouts
Retrieve a payout list
retrievePayoutList 7 params → 201400401404
GET
/api/payouts/{payout_id}
Retrieve a payout
retrievePayout 3 params → 200400401404

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are Payout (6 properties), Error-v2 (3 properties). Each schema is shown below with its type and property counts.

Payout-State
string
The state of the payout.
Payout-Amount
integer
The total amount of the payout in minor currency units. For example, 7034 represents €70.34.
Currency
string
[ISO 4217](https://en.wikipedia.org/wiki/ISO4217) currency code in upper case. :::info For more information about the supported currencies, see: [Help Center](…
Error-v2
object
3 properties
Payout-Destination-Type
string
The destination of the payout funds when a merchant initiates a withdrawal from their merchant account. | Destination type | Description | | ---------------- |…
Payout
object
6 properties 4 required
Payout-Id
string
Permanent payout ID used for payouts operations.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

revolut-payouts-api-openapi.yml Raw ↑

Other APIs Revolut publishes across the network.

Revolut Accounting API
Revolut Accounting categories API
Revolut Accounts API
Revolut Apple Pay merchant registration API
Revolut Applications API
Revolut Balance API
Revolut Card invitations API
Revolut Cards API
Revolut Configuration API
Revolut Counterparties API
Revolut Customers API
Revolut Disputes API
Where this information came from

This is an independent, third-party profile of Revolut Payouts API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.