Holvi Consent API
PSU authentication and consent token exchange.
Holvi Consent API is one of 4 APIs that Holvi publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Consent. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and authentication docs.
This API exposes 2 operations across 2 paths, and defines 1 schema. It is described by OpenAPI 3.0.3, at version 2.0.
Requests are made against a single base URL, https://api.psd2.holvi.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 4
Holvi Consent API declares
4 security schemes
for authenticating requests.
An API key is passed in the header as X-Holvi-Client-Id (HolviClientId).
An API key is passed in the header as X-Holvi-Client-Secret (HolviClientSecret).
An API key is passed in the header as Signature (HolviSignatureHeader).
It accepts HTTP bearer tokens (JWT) (HolviBearer).
By default, every request must be authenticated.
HolviClientId— Client ID identifying the TPP application (from approved onboarding).HolviClientSecret— Client Secret authenticating the TPP (from approved onboarding).HolviSignatureHeader— Application-level HTTP message signature (Draft Cavage HTTP Signatures v10, RSA-SHA256, key = 2048-bit) over (request-target), Host, Date [, Content-Type, Dige…HolviBearer— PSU consent JWT access token from the consent token exchange.
Paths & Operations 2
Across 2 paths, the API surfaces 2 operations — 1 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.
PSU authentication and consent token exchange.
Schemas 1
The contract defines 1 schema that model the data the API accepts and returns. The most detailed is ConsentTokenResponse (3 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 Holvi 3
Other APIs Holvi publishes across the network.