C. Hoare & Co. Dynamic Client Registration API
OBIE Dynamic Client Registration (DCR) proxy — lets third-party providers submit a signed Software Statement Assertion to register an OAuth2 client with C. Hoare & Co. as part of TPP onboarding. Published on the developer portal as v3.1-RC1; the harvested contract is the shared OBIE client-registration standard.
C. Hoare & Co. Dynamic Client Registration API is one of 3 APIs that C. Hoare & Co. publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Dynamic Client Registration, OAuth2, Onboarding, and Open Banking. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.
This API exposes 4 operations across 2 paths, and defines 4 schemas. It is described by OpenAPI 3.0.1, at version v3.1.0.
Requests are made against the base URL https://api.hoaresbank.co.uk/open-banking/v3.1.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
C. Hoare & Co. Dynamic Client Registration API declares
1 security scheme
for authenticating requests.
It supports OAuth 2.0 (TPPOAuth2Security) using the clientCredentials flow.
TPPOAuth2Security— TPP client credential authorisation flow with the ASPSP. No scopes defined as per specification
Paths & Operations 4
Across 2 paths, the API surfaces 4 operations — 1 DELETE, 1 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.
Schemas 4
The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are OBRegistrationProperties1 (16 properties), RegistrationError (2 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from C. Hoare & Co. 2
Other APIs C. Hoare & Co. publishes across the network.