Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Yorkshire Building Society Event Subscriptions API

OBIE Read/Write Event Subscriptions API v3.1.2 - lets an onboarded TPP create, read and delete event subscriptions so it can receive aggregated-polling and real-time event notifications (for example consent revocation) for YBS and Chelsea Building Society Open Banking resources. FAPI-secured (OAuth2/OIDC, mTLS).

Yorkshire Building Society Event Subscriptions API is one of 6 APIs that Yorkshire Building Society publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Event Subscriptions, Notifications, and Open Banking. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and a getting-started guide.

This API exposes 4 operations across 2 paths, and defines 9 schemas. It is described by OpenAPI 3.0.1, at version v3.1.2.

Requests are made against the base URL https://ob-ybs.api.ybs.co.uk/open-banking/v3.1/aisp.

4 operations 2 paths 9 schemas 1 DELETE1 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
v3.1.2
Base URL
https://ob-ybs.api.ybs.co.uk/open-banking/v3.1/aisp
Authentication
OAuth 2.0
Terms of Service
Resource Areas
1

Authentication & Security 1

Yorkshire Building Society Event Subscriptions API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (TPPOAuth2Security) using the clientCredentials flow, exposing 3 scopes.

  • TPPOAuth2Security — TPP client credential authorisation flow with the ASPSP

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.

Event Subscriptions 4
POST
/event-subscriptions
Create Event Subscription
CreateEventSubscriptions 5 params body → 201400401403404405406429
GET
/event-subscriptions
Get Event Subscription
GetEventSubscriptions 4 params → 200400401403404405406429
PUT
/event-subscriptions/{EventSubscriptionId}
Change Event Subscription
ChangeEventSubscriptionsEventSubscriptionId 6 params body → 200400401403404405406429
DELETE
/event-subscriptions/{EventSubscriptionId}
Delete Event Subscription
DeleteEventSubscriptionsEventSubscriptionId 5 params → 204400401403404405406429

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are Links (5 properties), OBErrorResponse1 (4 properties), OBError1 (4 properties), OBEventSubscriptionsResponse1 (3 properties). Each schema is shown below with its type and property counts.

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:…
Links
object
Links relevant to the payload
5 properties 1 required
Meta
object
Meta Data relevant to the payload
3 properties
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
OBEventSubscription1
object
1 property 1 required
OBEventSubscriptionResponse1
object
3 properties 1 required
OBEventSubscriptionsResponse1
object
3 properties 1 required
Version
string
Version for the event notification.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

yorkshire-building-society-event-subscriptions-api-openapi.yaml Raw ↑

Other APIs Yorkshire Building Society publishes across the network.

Yorkshire Building Society Account Information API
Yorkshire Building Society Payment Initiation API
Yorkshire Building Society Confirmation of Funds API
Yorkshire Building Society Dynamic Client Registration API
Yorkshire Building Society Generate Access Token API