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

Barclays Funds Confirmation Consents API

The Funds Confirmation Consents API from Barclays — 2 operation(s) for funds confirmation consents.

Barclays Funds Confirmation Consents API is one of 64 APIs that Barclays publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Funds Confirmation Consents. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 3 operations across 2 paths, and defines 12 schemas. It is described by OpenAPI 3.2.0, at version v4.0.

Requests are made against the base URL https://telesto.api.barclays/open-banking/v3.1.

3 operations 2 paths 12 schemas 1 DELETE1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v4.0
Base URL
https://telesto.api.barclays/open-banking/v3.1
Authentication
OAuth 2.0, OAuth 2.0
Resource Areas
1

Authentication & Security 2

Barclays Funds Confirmation Consents API declares 2 security schemes for authenticating requests. It supports OAuth 2.0 (TPPOAuth2Security) using the clientCredentials flow, exposing 1 scope. It supports OAuth 2.0 (PSUOAuth2Security) using the authorizationCode flow, exposing 1 scope.

  • TPPOAuth2Security — TPP client credential authorisation flow with the ASPSP
  • PSUOAuth2Security — OAuth flow, it is required when the PSU needs to perform SCA with the ASPSP when a TPP wants to access an ASPSP resource owned by the PSU

Paths & Operations 3

Across 2 paths, the API surfaces 3 operations — 1 DELETE, 1 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Funds Confirmation Consents 3
POST
/funds-confirmation-consents
Create a Funds Confirmation Consent
CreateFundsConfirmationConsents 5 params body → 201400401500403415405406
GET
/funds-confirmation-consents/{consentId}
Get a Funds Confirmation Consent
GetFundsConfirmationConsentsConsentId 6 params → 200400401500403405406429
DELETE
/funds-confirmation-consents/{consentId}
Delete a Funds Confirmation Consent
DeleteFundsConfirmationConsentsConsentId 6 params → 400401500204403405406429

Schemas 12

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

OBInternalConsentStatus1Code
string
Specifies the status of consent resource in code form. For a full list of values refer to OBInternalConsentStatus1Code in OBInternalCodeSet [here](https://gith…
Links
object
Links relevant to the payload
5 properties 1 required
OBStatusReason
object
3 properties
OBErrorResponse1
object
An array of detail error codes, and messages, and URLs to documentation to help remediation.
4 properties 1 required
OBFundsConfirmationConsentResponse1
object
3 properties 1 required
OBError1
object
4 properties 1 required
OBFundsConfirmationConsent1
object
1 property 1 required
OBExternalStatusReason1Code
string
Low level textual error code, for all enum values see OBExternalStatusReason1Code in OBInternalCodeSet [here](https://github.com/OpenBankingUK/ExternalInternal…
Meta
object
Meta Data relevant to the payload
3 properties
ExternalProxyAccountType1Code
string
Specifies the external proxy account type code, as published in the proxy account type external code set. For a full list of values refer to ExternalProxyAccou…
OBProxy1
object
Specifies an alternate assumed name for the identification of the account.
3 properties 2 required
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:…

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

barclays-funds-confirmation-consents-api-openapi.yml Raw ↑

Other APIs Barclays publishes across the network.

Barclays Smartpay Web Payment API
Barclaycard Smartpay Connect API
Barclays Corporate Payment Initiation API
Barclays Balances and Transactions Reporting API
Barclays Account Access Consents API
Barclays Accounts API
Barclays Apply Product External API OAS API
Barclays Atms API
Barclays Balances API
Barclays Beneficiaries API
Barclays Branches API
Barclays Business Current Accounts API
Where this information came from

This is an independent, third-party profile of Barclays Funds Confirmation Consents 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.