How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

OFX Open Banking API

The Open Banking API from OFX — 5 operation(s) for open banking.

OFX Open Banking API is one of 8 APIs that OFX publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 16 JSON Schema definitions.

Tagged areas include Open Banking. The published artifact set on APIs.io includes an OpenAPI specification and 16 JSON Schemas.

This API exposes 5 operations across 5 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version 2026-09-22.

Requests are made against a single base URL, https://beta.api.ofx.com.

5 operations 5 paths 6 schemas 3 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2026-09-22
Base URL
https://beta.api.ofx.com
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

OFX Open Banking API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (OAuth_2.0) using the clientCredentials and authorizationCode flows, exposing 1 scope. By default, every request must be authenticated.

Paths & Operations 5

Across 5 paths, the API surfaces 5 operations — 3 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Open Banking 5
POST
/open-banking/v3.1/aisp/account-access-consents
Create Account Access Consents
post_open_banking_v3_1_aisp_account_access_consents 2 params body → 201
GET
/open-banking/v3.1/aisp/accounts
Get Accounts
get_open_banking_v3_1_aisp_accounts 2 params → 200
GET
/open-banking/v3.1/pisp/deal/{DealId}
Get Deal Details
get_open_banking_v3_1_pisp_deal_DealId 3 params → 200
POST
/open-banking/v3.1/pisp/payment-consent
Create Payment Consent
post_open_banking_v3_1_pisp_payment_consent 2 params body → 201
GET
/open-banking/v3.1/pisp/payment-flow
Get Payment Flow
get_open_banking_v3_1_pisp_payment_flow 3 params → 302

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are GetOpenBankingV31PispDealDealidResponse (17 properties), GetOpenBankingV31AispAccountsResponse (10 properties), PostOpenBankingV31AispAccountAccessConsentsResponse (7 properties), PostOpenBankingV31PispPaymentConsentResponse (6 properties). Each schema is shown below with its type and property counts.

GetOpenBankingV31AispAccountsResponse
object
10 properties
PostOpenBankingV31AispAccountAccessConsentsRequest
object
6 properties 3 required
PostOpenBankingV31AispAccountAccessConsentsResponse
object
7 properties
GetOpenBankingV31PispDealDealidResponse
object
17 properties
PostOpenBankingV31PispPaymentConsentResponse
object
6 properties
PostOpenBankingV31PispPaymentConsentRequest
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

ofx-open-banking-api-openapi.yml Raw ↑

Other APIs OFX publishes across the network.

OFX Authorization Code API
OFX Authorize API
OFX Business API
OFX OAuth API
OFX Ofxrates API
OFX Refresh Token API
OFX Token API
Where this information came from

This is an independent, third-party profile of OFX Open Banking API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.