Skip to content

Account and Transaction API Specification API

by openbanking.org.uk

OAuthHTTPSFinance
Open documentation ↗

Overview

Swagger for Account and Transaction API Specification

Account and Transaction API Specification is a finance API from openbanking.org.uk. Requests are authenticated with OAuth. It is served over HTTPS. Its OpenAPI description documents 29 endpoints.

At a glance

Authentication
OAuth
HTTPS
Yes
CORS
Unknown
Category
Finance
Base URL
https://openbanking.org.uk
Version
3.1.7
Endpoints
29
Spec updated
2021-03-07

Make a first request

Replace the placeholders; the documentation says exactly where credentials go.

cURL
curl -X GET "https://openbanking.org.uk/accounts" \
  -H "Accept: application/json" \
  -H "Authorization: Bearer YOUR_TOKEN"
JavaScript
const response = await fetch("https://openbanking.org.uk/accounts", {
  method: "GET",
  headers: {
    "Accept": "application/json",
    "Authorization": "Bearer YOUR_TOKEN",
  },
});
const data = await response.json();
console.log(data);
Python
import requests

response = requests.request(
    "GET",
    "https://openbanking.org.uk/accounts",
    headers={
    "Accept": "application/json",
    "Authorization": "Bearer YOUR_TOKEN",
    },
    timeout=30,
)
print(response.json())

Endpoints

MethodPathWhat it does
POST/account-access-consentsCreate Account Access Consents
GET/account-access-consents/{ConsentId}Get Account Access Consents
DELETE/account-access-consents/{ConsentId}Delete Account Access Consents
GET/accountsGet Accounts
GET/accounts/{AccountId}Get Accounts
GET/accounts/{AccountId}/balancesGet Balances
GET/accounts/{AccountId}/beneficiariesGet Beneficiaries
GET/accounts/{AccountId}/direct-debitsGet Direct Debits
GET/accounts/{AccountId}/offersGet Offers
GET/accounts/{AccountId}/partiesGet Parties
GET/accounts/{AccountId}/partyGet Parties
GET/accounts/{AccountId}/productGet Products
GET/accounts/{AccountId}/scheduled-paymentsGet Scheduled Payments
GET/accounts/{AccountId}/standing-ordersGet Standing Orders
GET/accounts/{AccountId}/statementsGet Statements
GET/accounts/{AccountId}/statements/{StatementId}Get Statements
GET/accounts/{AccountId}/statements/{StatementId}/fileGet Statements
GET/accounts/{AccountId}/statements/{StatementId}/transactionsGet Transactions
GET/accounts/{AccountId}/transactionsGet Transactions
GET/balancesGet Balances
GET/beneficiariesGet Beneficiaries
GET/direct-debitsGet Direct Debits
GET/offersGet Offers
GET/partyGet Parties
GET/productsGet Products
GET/scheduled-paymentsGet Scheduled Payments
GET/standing-ordersGet Standing Orders
GET/statementsGet Statements
GET/transactionsGet Transactions

Questions

Does the Account and Transaction API Specification API need an API key?

Yes. The Account and Transaction API Specification API uses OAuth authentication; the documentation explains how to get credentials.

Does the Account and Transaction API Specification API support HTTPS?

Yes, the Account and Transaction API Specification API is served over HTTPS.

How many endpoints does the Account and Transaction API Specification API have?

Its OpenAPI description lists 29 endpoints in version 3.1.7. All of them are shown on this page.

What are alternatives to the Account and Transaction API Specification API?

Other Finance APIs include Stripe, SEC EDGAR Data, Plaid, Fed Treasury, Razorpay IFSC.

Compare alternatives →

Listed from APIs.guru (CC0).