API Reference
The integration guides provide step-by-step instructions for our most common use cases and once you’ve registered for a developer account and received your API key, you can login to make live API requests in our demo environment.
collect
Find Funding Accounts
Get Funding Transaction
Get Sender Details
Emulate inbound funds
Accept or Reject Inbound Transaction
convert
Create Conversion
Get Conversion
Find Conversions
Quote Conversion Cancellation
Cancel a Conversion
Quote Conversion Date Change
Conversion Date Change
Retrieve Profit / Loss
Split Preview
Conversion Split
Conversion Split History
Get Basic Rates
This endpoint is intended to provide an indication of the rate available in the market and can support requests for multiple currency pairs, so is good for polling requirements such as live FX ticker widgets. This endpoint should be used where speed, availability and the ability to request multiple currency pairs is important.
Get Detailed Rates
This endpoint provides a current tradeable rate for a single currency pair. It should be used as the start of the flow before a conversion is booked. This endpoint should be used where accuracy is the most important aspect, such as when a trade is about to be booked.
Create Held Rate Quote
BETA
Please note that this endpoint is currently in beta. For additional details, please contact your Account Manager or our support team.
Requests a new quote for the specified held-rate period and returns the details of the quote on success.
manage
Login
Submit a login ID and API key for a Currencycloud account, you can register for and API key here. A temporary authentication token is returned following a succesful login.
The authentication token is required to make requests to all other endpoints in the Currencycloud API. Tokens expire after 30 minutes of inactivity.
Token requests are limited to 60 calls per minute.
For security, Currencycloud accounts are disabled when four unsuccessful login attempts are made within a short period. In these circumstances, account holders must contact support to reactivate their account.
Logout
Create Account
UPCOMING CHANGES
As part of our Future-Ready program, this endpoint will be updated on 30 October 2026. The changes to field requirements are detailed in the field documentation below. Please note that additional fields are becoming mandatory.
Creates a new sub-account. Returns the new account entity on success.
Get Account
Update Account
Get Account's Compliance Settings
Update Account's Compliance Settings
Get Authenticating Account
Find Accounts
Get Payment Charges Settings
Manage Account Payment Charges Settings
Accept Terms of Use
Get Balance
Find Balances
Top Up Margin Balance
Get Authenticating Contact
Find Contacts
Get Contact
Update Contact
Create Contact
Generate HMAC Key for Contact
Find Bank Details
Get Beneficiary Requirements
Get Conversion Dates
Many currencies are triangulated; this means that holidays affecting the intermediary currency, as well as the sale and purchase currencies, will impact transactions. Find out more at our support article.
Get Available Currencies
Get Payer Requirements
Get Payment Dates
Get Payment Fee Rules
Get Payment Purpose Codes
Get Settlement Accounts
Generate Conversion Report
Generate Payment Report
Find Report Requests
Retrieves a Report Request with the given ID
Find Transactions
Get Transaction
Find Withdrawal Account
Pull Funds From Withdrawal Account
pay
Find Beneficiaries
Deprecation Notice: Request field name is deprecated and should no longer be used. It will be removed on 10 January 2027.
Returns beneficiaries attached to the account or any sub-account owned by the authenticated user.
Get Beneficiary
Update Beneficiary
- email and business_nature will be removed on 26 November 2026
- name will be removed on 10 January 2027
Updates an existing beneficiary. Returns the updated beneficiary entity on success.
Please note that it's not possible to change a beneficiary's entity type (company or individual) by an update. To achieve this, you should create a new beneficiary.
Create Beneficiary
- email and business_nature will be removed on 26 November 2026
- name will be removed on 10 January 2027
Creates a new beneficiary. Returns the new beneficiary entity on success.
Delete Beneficiary
Validate Beneficiary
Verify Beneficiary Account
CoP and VoP are both peer-to-peer name-checking service designed to help reduce misdirected payments and provide greater assurance that payments are being sent, and collected from, the intended account holder for domestic payments.
Currently, access is restricted to UK and EU institutions and in-scope clients.
We plan to add more market coverage to this API in the future, thereby extending access to additional clients.
If you're interested in learning more or have received notification that you're in-scope, please contact your Account Manager or our support team.
Create Payment
Deprecation Notice: Request field ultimate_beneficiary_name is deprecated and should no longer be used. It will be removed on 26 November 2026
Submits a payment. On success, returns the new payment record. Use the Get Payer Requirements endpoint to find out what payer information needs to be provided.
Clients who are implementing Strong Customer Authentication (SCA) for payments should refer to our integration guide.
Find Payments
Get Payment
Update Payment
Deprecation Notice: Request field ultimate_beneficiary_name is deprecated and should no longer be used. It will be removed on 26 November 2026
'Updates a payment. On success, returns the updated payment entity.'
Get Payment Confirmation
Get Payment Submission Information
Delete Payment
Get Payment Tracking Information
Get Payment Delivery Date
Get Quote Payment Fee
Validate Payment
Deprecation Notice: Request field ultimate_beneficiary_name is deprecated and should no longer be used. It will be removed on 26 November 2026
Validates the details of a new payment without creating a record of the payment. On success, returns an object containing a string validation_result with value "success".
Clients who are implementing Strong Customer Authentication (SCA) for payments should refer to our SCA for payments integration guide.