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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
C. Hoare & Co.

C. Hoare & Co. Scheduled Payments API

The Scheduled Payments API from C. Hoare & Co. — 2 operation(s) for scheduled payments.

Documentation Provider Profile APIs.io OpenAPI GitHub

C. Hoare & Co. Scheduled Payments 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 Scheduled Payments. 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 17 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 17 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
Contact
Service Desk
License
open-licence
Terms of Service
View terms
Resource Areas
1

Authentication & Security 2

C. Hoare & Co. Scheduled Payments 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.

Scheduled Payments 2
GET
/accounts/{AccountId}/scheduled-payments
Get Scheduled Payments
GetAccountsAccountIdScheduledPayments 7 params → 200400401403404405406429
GET
/scheduled-payments
Get Scheduled Payments
GetScheduledPayments 6 params → 200400401403404405406429

Schemas 17

The contract defines 17 schemas that model the data the API accepts and returns. The most detailed are OBScheduledPayment2Detail (8 properties), OBScheduledPayment2Basic (6 properties), Links (5 properties), OBError1 (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
OBScheduledPayment2Detail
object
8 properties 5 required
OBReadScheduledPayment2
object
3 properties 3 required
Meta
object
Meta Data relevant to the payload
3 properties
OBExternalScheduleType1Code
string
Specifies the scheduled payment date type requested
OBError1
object
4 properties 2 required
OBErrorResponse1
object
An array of detail error codes, and messages, and URLs to documentation to help remediation.
4 properties 3 required
OBActiveOrHistoricCurrencyAndAmount
object
Amount of money of the cash balance after a transaction entry is applied to the account..
2 properties 2 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:…
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.
OBScheduledPayment2Basic
object
6 properties 4 required
OBScheduledPayment2
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.
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-scheduled-payments-api-openapi.yml Raw ↑

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

C. Hoare & Co. Account Access API
AE Profile APIs.io
C. Hoare & Co. Accounts API
AE Profile APIs.io
C. Hoare & Co. Balances API
AE Profile APIs.io
C. Hoare & Co. Beneficiaries API
AE Profile APIs.io
C. Hoare & Co. Client Registration API
AE Profile APIs.io
C. Hoare & Co. Direct Debits API
AE Profile APIs.io
C. Hoare & Co. Domestic Payments API
AE Profile APIs.io
C. Hoare & Co. Domestic Scheduled Payments API
AE Profile APIs.io
C. Hoare & Co. Domestic Standing Orders API
AE Profile APIs.io
C. Hoare & Co. File Payments API
AE Profile APIs.io
C. Hoare & Co. International Payments API
AE Profile APIs.io
C. Hoare & Co. International Scheduled Payments API
AE Profile APIs.io
#Scheduled Payments
← Back to C APIs
API Details
ID
c-hoare-and-co:c-hoare-and-co-scheduled-payments-api
Base URL
https://api.hoaresbank.co.uk/open-banking/v3.1/aisp
Docs
https://developer.hoaresbank.co.uk/apis/ob-account-and-transaction-api-v3-1-0/docs
Provider
C. Hoare & Co.
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

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.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=c-hoare-and-co-scheduled-payments-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/c-hoare-and-co-scheduled-payments-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

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. Scheduled Payments 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.