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

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.2.0, at version 1.0.0-3030f99c.

Requests are made against 2 base URLs: https://api.enablebanking.com, https://api.tilisy.com.

4 operations 3 paths 24 schemas 1 DELETE1 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0-3030f99c
Base URL
https://api.enablebanking.com
Authentication
HTTP Bearer
Resource Areas
1

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.

User sessions 4
POST
/auth
Start user authorization
initialize_session_auth_post body → 200400401403404408422429
POST
/sessions
Authorize user session
authorize_session_sessions_post body → 200400401403404408422429
GET
/sessions/{session_id}
Get session data
get_session_sessions__session_id__get 1 param → 200400401403404408422429
DELETE
/sessions/{session_id}
Delete session
delete_session_sessions__session_id__delete 9 params → 200400401403404408422429

Schemas 24

The contract defines 24 schemas that model the data the API accepts and returns. The most detailed are AccountResource (16 properties), GetSessionResponse (10 properties), PostalAddress (10 properties), StartAuthorizationRequest (10 properties). Each schema is shown below with its type and property counts.

PSUType
string
PostalAddress
object
10 properties
ErrorCode
string
FinancialInstitutionIdentification
object
3 properties
CashAccountType
string
ClearingSystemMemberIdentification
object
2 properties
ErrorResponse
object
4 properties 1 required
SuccessResponse
object
1 property
AccountResource
object
16 properties 4 required
GenericIdentification
object
3 properties 2 required
AmountType
object
2 properties 2 required
AccountIdentification
object
2 properties
ASPSP
object
2 properties 2 required
AuthorizeSessionRequest
object
1 property 1 required
AuthorizeSessionResponse
object
5 properties 5 required
SessionAccount
object
3 properties 3 required
StartAuthorizationRequest
object
10 properties 4 required
SchemeName
string
SessionStatus
string
StartAuthorizationResponse
object
3 properties 3 required
AddressType
string
Usage
string
Access
object
4 properties 1 required
GetSessionResponse
object
10 properties 8 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

enable-banking-user-sessions-api-openapi.yml Raw ↑

Other APIs Enable Banking publishes across the network.

Enable Banking Accounts data API
Enable Banking Misc API
Enable Banking Payments API
Where this information came from

This is an independent, third-party profile of Enable Banking User sessions 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.