Global Bank Account Information

Access +2600 european banks with one single entry point.

Access Real-Time Financial Data through Open Banking with our Global Bank Account Information API. The API allows secure access to bank account information with user consent, enabling businesses to retrieve real-time financial data, such as balances, transaction history, and verification details. This API streamlines financial processes, improves customer insights, and ensures compliance by providing up-to-date, trusted information directly from verified bank accounts.

With this API, you can:

• Retrieve real-time bank account balances and transaction history
• Verify account details for customer onboarding and financial assessments
• Enhance insights into customer financial behavior

Use case:

A financial lender uses the Global Bank Account Information API to securely access a customer's bank transaction history and balance, improving the accuracy of loan eligibility assessments while maintaining compliance with financial regulations.

Read more in this link on how to test the service in sandbox.

Integration guide for paginating through transaction history on the Global Bank Account Data API.

Overview

The GET /account/{accountId}/transactions endpoint returns a continuation_key whenever the bank has more transactions than fit in a single response. Pass that value back to fetch the next page.

Follow-up pages are free. Only the first request in a pagination sequence is billed; every subsequent request that carries a valid continuationKey is recorded as 0 credits.

Endpoint

GET https://api.roaring.io/global/bank-account-data/1.0/account/{accountId}/transactions

Parameters

If both fromDate and toDate are omitted the bank's default window is used.

Response

{
  "transactions": [
    { "...": "..." }
  ],
  "continuation_key": "eyJjayI6Ii4uLiIsImNvIjoiYWJjLi4uIiwiYWMiOiJhY2MtMSIsImV4IjoxNzQ4ODAwMDAwfQ.6f2c1e..."
}

• transactions — array of transaction records as returned by Enable Banking.
• continuation_key — present only when more pages remain. When the field is missing or empty, you have reached the end of the result set.

How to paginate

1. Make the first request with fromDate / toDate (and no continuationKey). This call is billed normally.
2. If the response contains continuation_key, re-issue the same request with continuationKey set to that value. This call is free.
3. Repeat step 2 until the response no longer contains continuation_key.

⚠️ When paginating, send the same accountId and the same authentication headers that you used for the first request. Tokens are bound to both — see Token rules below.

💡 fromDate and toDate are not required on follow-up requests — the bank applies the same window that produced the token. You may include them for clarity; they are ignored upstream when a continuation_key is present.

Example — iterate all pages

import requests

base_url = "https://api.roaring.io/global/bank-account-data/1.0"
headers = {
    "Authorization": "Bearer <access_token>",
    "roaring-consumer-key": "<consumer_key>",
}

params = {"fromDate": "2026-01-01", "toDate": "2026-03-31"}
all_tx = []

while True:
    r = requests.get(
        f"{base_url}/account/{account_id}/transactions",
        params=params,
        headers=headers,
    )
    r.raise_for_status()
    body = r.json()

    all_tx.extend(body.get("transactions", []))

    token = body.get("continuation_key")
    if not token:
        break
    params = {"continuationKey": token}

# First page (billed)
curl -H "Authorization: Bearer $TOKEN" \
     -H "roaring-consumer-key: $CONSUMER_KEY" \
     "https://api.roaring.io/global/bank-account-data/1.0/account/$ACC/transactions?fromDate=2026-01-01&toDate=2026-03-31"

# Next page (free)
curl -H "Authorization: Bearer $TOKEN" \
     -H "roaring-consumer-key: $CONSUMER_KEY" \
     "https://api.roaring.io/global/bank-account-data/1.0/account/$ACC/transactions?continuationKey=eyJjay..."

Billing

Free-tier accounting is performed server-side; no action is required from your side beyond passing the token back.

Token rules

Treat the continuation_key as opaque — do not parse or modify it; format and length may change without notice.

The token is bound to the request that produced it:

• It only works with the same roaring-consumer-key that received it.
• It only works with the same accountId.
• It is valid for 1 hour. After that, restart the sequence with a fresh first request.

If any of these conditions are violated the call returns 400 Invalid or expired continuation key and is not charged.

Errors

A 400 response on a follow-up page is not charged, so a failed pagination call has no billing impact.

FAQ

How do I know when I've reached the last page? The last response has no continuation_key field (or returns it empty). Stop iterating at that point.

Can I skip ahead or go backwards? No. The continuation_key represents the bank's cursor state, so pages must be fetched in order. If you need an earlier page, restart from the first request.

Does the token survive a service restart on my side? Yes, for up to 1 hour. The token is self-contained — you may persist it across processes as long as the expiry hasn't passed and the consumer/account context is the same.

What if walking the full history takes longer than 1 hour? Restart the sequence with a fresh first request. In practice an hour is generous; most full walks complete in seconds.