Enable Banking User sessions API
The User sessions API from Enable Banking — 3 operation(s) for user sessions.
Enable Banking User sessions API is one of 4 APIs that Enable Banking publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
This API exposes 4 JSON Schema definitions.
Tagged areas include User sessions. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a getting-started guide, a JSON-LD context, pricing, an engineering blog, and 4 JSON Schemas.
This API exposes 4 operations across 3 paths, and defines 24 schemas. It is described by OpenAPI 3.1.0, at version 1.0.0-3030f99c.
Requests are made against 2 base URLs: https://api.enablebanking.com, https://api.tilisy.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Enable Banking User sessions API declares
1 security scheme
for authenticating requests.
It accepts HTTP bearer tokens (JWT) (bearerAuth).
By default, every request must be authenticated.
bearerAuth— In order to get access to this API you need to: - Generate a private RSA key and a self-signed certificate; - Upload the certificate to enablebanking.com and g…
Paths & Operations 4
Across 3 paths, the API surfaces 4 operations — 1 DELETE, 1 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.
Schemas 24
The contract defines 24 schemas that model the data the API accepts and returns. The most detailed are AccountResource (16 properties), StartAuthorizationRequest (10 properties), GetSessionResponse (10 properties), PostalAddress (10 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 Enable Banking 3
Other APIs Enable Banking publishes across the network.