| Crates.io | revolut |
| lib.rs | revolut |
| version | 0.1.4 |
| created_at | 2025-03-08 08:01:53.925675+00 |
| updated_at | 2025-08-02 18:22:41.785747+00 |
| description | A library to communicate with the Revolut API |
| homepage | |
| repository | https://github.com/curriedsoftware/revolut |
| max_upload_size | |
| id | 1584181 |
| size | 358,710 |
Revolut API integration for Rust.
[!NOTE] This crate has no relationship with Revolut Ltd, as such, it is an unofficial implementation that uses the documented public API endpoints.
[!CAUTION] This crate is in its very early stages and is expected to be incomplete and might contain critical bugs. Do not use it in a production environment in its current state.
Follow the instructions at the Revolut API documentation site.
In order to issue requests in the general case, two settings are necessary:
The library will automatically request new access tokens when the cached one expires, or when it performs the first request in cold state.
$ REVOLUT_CLIENT_ASSERTION='<CLIENT_ASSERTION>' REVOLUT_REFRESH_TOKEN='<REFRESH_TOKEN>' just list-accounts
Generating a new access token requires the authorization code that was granted in step Setting up Business API along with the client assertion.
$ REVOLUT_CLIENT_ASSERTION='<CLIENT_ASSERTION>' REVOLUT_AUTHORIZATION_CODE='<AUTHORIZATION_CODE>' just retrieve-access-token
Refreshing the access token requires the refresh token that was granted in step Setting up Business API along with the client assertion.
$ REVOLUT_CLIENT_ASSERTION='<CLIENT_ASSERTION>' REVOLUT_AUTHORIZATION_CODE='<AUTHORIZATION_CODE>' just refresh-access-token
Follow the instructions at the Revolut API documentation site.
In order to initiate requests, you need to provide:
In order to communicate with the Revolut Merchant API, you will need to have set up the Merchant API.
$ REVOLUT_SECRET_KEY='<SECRET_KEY>' just list-orders