Revolut Latvia API Access via Open Banking Sync

Pull live Revolut (Latvia) data into your product without wrestling with per-bank certificates or bespoke integrations. open-banking.io wraps Revolut behind a single, standardised API so you can read account details, balances and transaction history the moment a customer grants consent. Whether the underlying profile is a Revolut business or personal account, the same endpoints and response shapes apply — write your integration once and reuse it across 2,600+ EU and UK banks.

How to connect Revolut

  1. Register for an open-banking.io API key and point your app at the Revolut (Latvia) endpoint.
  2. Send your user to the hosted Revolut authorisation screen — no certificates or eIDAS setup required on your side.
  3. The customer authenticates directly with Revolut (BIC REVOLT21) and approves the data scopes you requested.
  4. Receive the access token and start calling accounts, balances and transactions immediately.
  5. Refresh silently within the consent window, then re-prompt when it lapses.

What data you can access

  • Accounts — identifiers, currency, product type and holder metadata for business and personal profiles.
  • Balances — current and available amounts, updated in near real time.
  • Transactions — booked and pending entries with amounts, dates, counterparties and remittance details.

A single Revolut consent stays valid for up to 180 days before the customer needs to re-authorise, giving you a long window for uninterrupted syncing. Revolut sits alongside more than 2,600 other institutions on the same interface, so adding further banks later is a configuration change, not a new build.

Privacy by design

open-banking.io is zero-knowledge: credentials never touch your servers and we don't retain the banking data that flows through. Because the platform is certificate-free, you skip the QWAC/QSEAL burden that usually gates PSD2 access — cutting both setup time and compliance overhead.

Pricing

One flat subscription of roughly EUR 3/month covers Revolut and every other supported bank. No per-call metering, no per-connection surcharges.

FAQ

Does this work for both Revolut business and personal accounts?

Yes. Both account types are supported through the same endpoints, so your code handles either without branching.

Do I need my own PSD2 certificates?

No. The API is certificate-free — open-banking.io handles the regulated access layer, so you integrate with a plain API key.

How long before I have to re-authorise a customer?

Revolut consents last up to 180 days. After that, a quick re-authorisation restores access.

Ready to start syncing Revolut data? Explore the full platform at open-banking.io.