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

C. Hoare & Co. Accounts API

The Accounts API from C. Hoare & Co. — 2 operation(s) for accounts.

C. Hoare & Co. Accounts API is one of 20 APIs that C. Hoare & Co. publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Account. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 2 operations across 2 paths, and defines 16 schemas. It is described by OpenAPI 3.2.0, at version v3.1.0.

Requests are made against a single base URL, https://api.hoaresbank.co.uk/open-banking/v3.1/aisp.

2 operations 2 paths 16 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v3.1.0
Base URL
https://api.hoaresbank.co.uk/open-banking/v3.1/aisp
Authentication
OAuth 2.0, OAuth 2.0
Terms of Service
Resource Areas
1

Authentication & Security 2

C. Hoare & Co. Accounts API declares 2 security schemes for authenticating requests. It supports OAuth 2.0 (PSUOAuth2Security) using the authorizationCode flow, exposing 1 scope. It supports OAuth 2.0 (TPPOAuth2Security) using the clientCredentials flow, exposing 1 scope.

  • PSUOAuth2Security — OAuth flow, it is required when the PSU needs to perform SCA with the ASPSP when a TPP wants to access an ASPSP resource owned by the PSU
  • TPPOAuth2Security — TPP client credential authorisation flow with the ASPSP

Paths & Operations 2

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

Accounts 2
GET
/accounts
Get Accounts
GetAccounts 6 params → 200400401403404405406429
GET
/accounts/{AccountId}
Get Accounts
GetAccountsAccountId 7 params → 200400401403405406429500

Schemas 16

The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are OBAccount3Detail (8 properties), OBAccount3Basic (6 properties), Links (5 properties), OBErrorResponse1 (4 properties). Each schema is shown below with its type and property counts.

AccountId
string
A unique and immutable identifier used to identify the account resource. This identifier has no meaning to the account owner.
Links
object
Links relevant to the payload
5 properties 1 required
Meta
object
Meta Data relevant to the payload
3 properties
OBError1
object
4 properties 2 required
OBReadAccount3
object
3 properties 3 required
OBErrorResponse1
object
An array of detail error codes, and messages, and URLs to documentation to help remediation.
4 properties 3 required
OBBranchAndFinancialInstitutionIdentification5
object
Party that manages the account on behalf of the account owner, that is manages the registration and booking of entries on the account, calculates balances on t…
2 properties 2 required
ISODateTime
string
All dates in the JSON payloads are represented in ISO 8601 date-time format. All date-time fields in responses must include the timezone. An example is below:…
OBAccount3Basic
object
Unambiguous identification of the account to which credit and debit entries are made.
6 properties 4 required
OBAccount3Detail
object
Unambiguous identification of the account to which credit and debit entries are made.
8 properties 5 required
OBAccount3
OBCashAccount5
object
Provides the details to identify the beneficiary account.
4 properties 2 required
OBExternalAccountIdentification4Code
string
Name of the identification scheme, in a coded form as published in an external list.
OBExternalAccountType1Code
string
Specifies the type of account (personal or business).
OBExternalAccountSubType1Code
string
Specifies the sub type of account (product family group).
OBExternalFinancialInstitutionIdentification4Code
string
Name of the identification scheme, in a coded form as published in an external list.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

c-hoare-and-co-accounts-api-openapi.yml Raw ↑

Other APIs C. Hoare & Co. publishes across the network.

C. Hoare & Co. Account Access API
C. Hoare & Co. Balances API
C. Hoare & Co. Beneficiaries API
C. Hoare & Co. Client Registration API
C. Hoare & Co. Direct Debits API
C. Hoare & Co. Domestic Payments API
C. Hoare & Co. Domestic Scheduled Payments API
C. Hoare & Co. Domestic Standing Orders API
C. Hoare & Co. File Payments API
C. Hoare & Co. International Payments API
C. Hoare & Co. International Scheduled Payments API
C. Hoare & Co. International Standing Orders API
Where this information came from

This is an independent, third-party profile of C. Hoare & Co. Accounts 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.