canonical: https://jentic.com/apis/revolut.com/business-api

# Revolut Business API

As a Revolut Business customer with a Business Account, you can use the Business API to automate your own business processes. Save time, reduce your costs, and avoid errors by using the Business API. You can view accounts, manage counterparties, make payments or currency exchanges without manual effort in the Web UI: - Accounting: [Account management](https://developer.revolut.com/docs/business/ac. The API exposes 50 endpoints secured with bearer authentication.

## For AI agents

Programmatically validate an account name (cop), retrieve all accounts. Covers 50 operations with bearer authentication.

## Scope

Does not handle communications, crm, or developer tools - use for payments only.

## Capabilities

- Validate an account name (CoP)
- Retrieve all accounts
- Create a card
- Query and filter Business API records by parameters
- Monitor Business API operational status and events

## Use cases

### Payments Operations

Use the Business API to perform payments operations programmatically. The API provides 50 endpoints covering core functionality including validate an account name (cop), retrieve all accounts, retrieve an account.

Example prompt: Call POST /account-name-validation to validate an account name (cop)

### Automated Accounts Management

Automate accounts operations by combining multiple Business API endpoints. Agents can retrieve all accounts and then retrieve an account in a single workflow.

Example prompt: Call GET /accounts to retrieve all accounts, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Business API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Example prompt: Search Jentic for 'validate an account name (cop)', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /account-name-validation | Validate an account name (CoP) |
| GET | /accounts | Retrieve all accounts |
| GET | /accounts/{account_id} | Retrieve an account |
| GET | /accounts/{account_id}/bank-details | Retrieve account's full bank details |
| POST | /cards | Create a card |
| GET | /cards | Retrieve a list of cards |
| GET | /cards/{card_id} | Retrieve card details |
| PATCH | /cards/{card_id} | Update card details |

## Key resources

- **Accounts** — Get the balances, full banking details, and other details of your business accounts. 

For more info
- **Cards** — Manage cards for the business team members, freeze, unfreeze, terminate and update card settings, su
- **Counterparties** — Manage counterparties that you intend to transact with.

Request and response examples can vary base
- **Expenses** — Get the list of all the expenses, or use the filters to narrow down the results.
You can also get a
- **Foreign exchange** — Retrieve information on exchange rates between currencies, buy and sell currencies.

For more inform

## Why Jentic

- **Setup:** Wiring the Revolut Business API by hand means handling its bearer token auth, choosing the live b2b.revolut.com or sandbox host, and managing retries yourself. Through Jentic you install once, import the Business API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Revolut Business puts the account id in the URL path (/accounts/{account_id}), so a rule can pin your agent to one account: it can read that account and its bank details and nothing else. You choose the operations it may call, so ones like creating or updating cards are not included unless you add them.
- **Credential handling:** Your Revolut Business token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'validate an account name' or 'get an account balance', and Jentic returns the matching Business API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Stripe** — Alternative payments API
- **Adyen** — Alternative payments API
- **Square** — Complementary payments API
- **Paypal** — Complementary payments API

## FAQ

### What authentication does the Business API use?

The Business API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I validate an account name (cop) with the Business API?

Yes. Use the POST /account-name-validation endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Business API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I validate an account name (cop) through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'validate an account name (cop)'. Jentic returns the matching Business API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Business API have?

The Business API exposes 50 endpoints covering accounts, cards, counterparties operations.

### Can I limit what my agent is allowed to do with the Revolut Business API?

Yes. Jentic One runs on your own infrastructure, and your rules decide which Business API operations and credentials the agent may use. Because Revolut puts the account id in the URL path, such as GET /accounts/{account_id}, you can pin the agent to a single account so it only reads that account and its bank details via GET /accounts/{account_id}/bank-details. You choose the operations it may call, so write actions like POST /cards or PATCH /cards/{card_id} stay out of reach unless you explicitly add them.