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. Statements API

The Statements API from C. Hoare & Co. — 5 operation(s) for statements.

C. Hoare & Co. Statements 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 Statements. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 5 operations across 5 paths, and defines 48 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.

5 operations 5 paths 48 schemas 5 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. Statements 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 5

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

Statements 5
GET
/accounts/{AccountId}/statements
Get Statements
GetAccountsAccountIdStatements 9 params → 200400401403404405406429
GET
/accounts/{AccountId}/statements/{StatementId}
Get Statements
GetAccountsAccountIdStatementsStatementId 8 params → 200400401403404405406429
GET
/accounts/{AccountId}/statements/{StatementId}/file
Get Statements
GetAccountsAccountIdStatementsStatementIdFile 8 params → 200400401403404405406429
GET
/accounts/{AccountId}/statements/{StatementId}/transactions
Get Transactions
GetAccountsAccountIdStatementsStatementIdTransactions 8 params → 200400401403404405406429
GET
/statements
Get Statements
GetStatements 8 params → 200400401403404405406429

Schemas 48

The contract defines 48 schemas that model the data the API accepts and returns. The most detailed are OBTransaction4Detail (23 properties), OBTransaction4Basic (16 properties), OBStatement1Detail (15 properties), OBStatement1Basic (14 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.
OBStatementInterest1
object
Set of elements used to provide details of a generic interest amount related to the statement resource.
3 properties 3 required
OBExternalStatementType1Code
string
Statement type, in a coded form.
Links
object
Links relevant to the payload
5 properties 1 required
OBTransactionCashBalance
object
Set of elements used to define the balance as a numerical representation of the net increases and decreases in an account after a transaction entry is applied…
3 properties 3 required
OBSupplementaryData1
object
Additional information that can not be captured in the structured fields and/or any other specific block.
OBExternalStatementValueType1Code
string
Statement value type, in a coded form.
OBBranchAndFinancialInstitutionIdentification6
object
Financial institution servicing an account for the debtor.
4 properties
OBExternalStatementInterestType1Code
string
Interest amount type, in a coded form.
OBStatementFee1
object
Set of elements used to provide details of a fee for the statement resource.
3 properties 3 required
OBCashAccount6
object
Unambiguous identification of the account of the debtor, in the case of a crebit transaction.
4 properties
OBExternalCardAuthorisationType1Code
string
The card authorisation type.
Meta
object
Meta Data relevant to the payload
3 properties
OBStatement1Detail
object
Provides further details on a statement resource.
15 properties 5 required
OBStatementBenefit1
object
Set of elements used to provide details of a benefit or reward amount for the statement resource.
2 properties 2 required
OBError1
object
4 properties 2 required
OBBankTransactionCodeStructure1
object
Set of elements used to fully identify the type of underlying transaction resulting in an entry.
2 properties 2 required
OBStatementAmount1
object
Set of elements used to provide details of a generic amount for the statement resource.
3 properties 3 required
OBExternalStatementRateType1Code
string
Statement rate type, in a coded form.
OBMerchantDetails1
object
Details of the merchant involved in the transaction.
2 properties
OBCurrencyExchange5
object
Set of elements used to provide details on the currency exchange.
7 properties 2 required
TransactionInformation
string
Further details of the transaction. This is the transaction narrative, which is unstructured text.
OBErrorResponse1
object
An array of detail error codes, and messages, and URLs to documentation to help remediation.
4 properties 3 required
OBTransaction4Basic
object
Provides further details on an entry in the report.
16 properties 5 required
OBActiveOrHistoricCurrencyAndAmount
object
Amount of money of the cash balance after a transaction entry is applied to the account..
2 properties 2 required
OBAddressTypeCode
string
Identifies the nature of the postal address.
OBStatementRate1
object
Set of elements used to provide details of a generic rate related to the statement resource.
2 properties 2 required
OBReadStatement1
object
3 properties 3 required
OBStatementDateTime1
object
Set of elements used to provide details of a generic date time for the statement resource.
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:…
OBTransaction4Detail
object
Provides further details on an entry in the report.
23 properties 5 required
OBExternalCardSchemeType1Code
string
Name of the card scheme.
OBExternalStatementAmountType1Code
string
Amount type, in a coded form.
OBReadTransaction4
object
3 properties 3 required
OBExternalFinancialInstitutionIdentification4Code
string
Name of the identification scheme, in a coded form as published in an external list.
OBStatement1Basic
object
Provides further details on a statement resource.
14 properties 5 required
OBExternalStatementDateTimeType1Code
string
Date time type, in a coded form.
OBExternalStatementFeeType1Code
string
Fee type, in a coded form.
OBStatementValue1
object
Set of elements used to provide details of a generic number value related to the statement resource.
2 properties 2 required
OBBalanceType1Code
string
Balance type, in a coded form.
OBExternalAccountIdentification4Code
string
Name of the identification scheme, in a coded form as published in an external list.
OBPostalAddress6
object
Information that locates and identifies a specific address, as defined by postal services.
10 properties
OBTransaction4
OBActiveCurrencyAndAmount_SimpleType
string
A number of monetary units specified in an active currency where the unit of currency is explicit and compliant with ISO 4217.
OBEntryStatus1Code
string
Status of a transaction entry on the books of the account servicer.
OBExternalStatementBenefitType1Code
string
Benefit type, in a coded form.
OBTransactionCardInstrument1
object
Set of elements to describe the card instrument used in the transaction.
4 properties 1 required
OBStatement1

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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

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

C. Hoare & Co. Account Access API
C. Hoare & Co. Accounts 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
Where this information came from

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