C. Hoare & Co. Domestic Standing Orders 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 Domestic Standing Orders. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.
This API exposes
4 operations
across 4 paths,
and defines 31 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/pisp.
4 operations4 paths31 schemas2 GET2 POST
Metadata
The identity and technical contract details declared by the specification.
C. Hoare & Co. Domestic Standing Orders 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 4
Across 4 paths, the API surfaces 4 operations — 2 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.
The contract defines 31 schemas that model the data the API accepts and returns. The most detailed are OBDomesticStandingOrder2 (12 properties), OBWriteDataDomesticStandingOrderConsentResponse2 (9 properties), OBWriteDataDomesticStandingOrderResponse2 (8 properties), Links (5 properties). Each schema is shown below with its type and property counts.
OBWriteDomesticStandingOrder2
object
2 properties2 required
OBMultiAuthorisation1
object
The multiple authorisation flow response from the ASPSP.
5 properties1 required
OBRisk1
object
The Risk section is sent by the initiating party to the ASPSP. It is used to specify additional details for risk scoring for Payments.
4 properties
OBExternalPermissions2Code
string
Specifies the Open Banking service request types.
OBDomesticStandingOrder2
object
The Initiation payload is sent by the initiating party to the ASPSP. It is used to request movement of funds from the debtor account to a creditor for a domest…
12 properties4 required
OBCashAccountCreditor3
object
Provides the details to identify the beneficiary account.
4 properties3 required
OBErrorResponse1
object
An array of detail error codes, and messages, and URLs to documentation to help remediation.
4 properties3 required
OBExternalAuthorisation1Code
string
Type of authorisation flow requested.
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:…
OBExternalPaymentChargeType1Code
string
Charge type, in a coded form.
OBSupplementaryData1
object
Additional information that can not be captured in the structured fields and/or any other specific block.
Meta
object
Meta Data relevant to the payload
3 properties
OBExternalConsentStatus1Code
string
Specifies the status of resource in code form.
Links
object
Links relevant to the payload
5 properties1 required
OBCashAccountDebtor4
object
Provides the details to identify the debtor account.
4 properties2 required
OBExternalPaymentContext1Code
string
Specifies the payment context
OBExternalStatus2Code
string
Specifies the status of the authorisation flow in code form.
OBExternalStatus1Code
string
Specifies the status of resource in code form.
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.
OBWriteDomesticStandingOrderConsent2
object
2 properties2 required
OBCharge2
object
Set of elements used to provide details of a charge for the payment initiation.
3 properties3 required
OBWriteDomesticStandingOrderConsentResponse2
object
4 properties4 required
OBWriteDataDomesticStandingOrder2
object
2 properties2 required
OBChargeBearerType1Code
string
Specifies which party/parties will bear the charges associated with the processing of the payment transaction.
OBError1
object
4 properties2 required
OBWriteDataDomesticStandingOrderConsent2
object
3 properties2 required
OBAuthorisation1
object
The authorisation type request from the TPP.
2 properties1 required
OBExternalAccountIdentification4Code
string
Name of the identification scheme, in a coded form as published in an external list.
OBWriteDomesticStandingOrderResponse2
object
3 properties3 required
OBWriteDataDomesticStandingOrderResponse2
object
8 properties6 required
OBWriteDataDomesticStandingOrderConsentResponse2
object
9 properties6 required
Specification
The full machine-readable OpenAPI contract behind this narrative.
Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.
Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.
MCP tools for apis
4 tools reach this content
search_api_evangelistSearch every content type across the network at once.
find_relatedThe shared-tag relevance graph — what else covers this.
get_tagEverything one tag labels, across all content types.
guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
A second provider on the same verified email joins the account you already have.
Your account
ⓘWhere this information came from
This is an independent, third-party profile of C. Hoare & Co. Domestic Standing Orders 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.
