Yapily

Yapily is a UK-headquartered Open Banking platform that exposes a single REST API across 2,000+ banks in the UK and 18+ European countries. The platform provides AISP (Account Information) and PISP (Payment Initiation) capabilities, Variable Recurring Payments (VRP), transaction enrichment (Data Plus), Account Validation, and Hosted Payment/Consent Pages. Yapily Connect Ltd is FCA-authorised in the UK and Yapily Connect UAB is authorised by the Bank of Lithuania for EU coverage, allowing customers to launch without holding their own PSD2 permissions.

Yapily publishes 16 APIs on the APIs.io network, including Institutions API, Consents and Authorisations API, Payments API (PIS), and 13 more. Tagged areas include Open Banking, AISP, PISP, Payments, and Account Information.

The Yapily catalog on APIs.io includes 1 JSON-LD context and 2 Spectral governance rulesets.

Yapily’s developer surface includes authentication, documentation, getting-started guide, tooling, code examples, pricing, engineering blog, and 16 more developer resources.

🌐 Visit website 📡 Source on GitHub

53.5/100 developing ▬ flat Agent 37/100 agent ready Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0

AccessPaid

5 APIs

Open Banking AISP PISP Payments Account Information Variable Recurring Payments Financial-Services PSD2 FCA Berlin Group UK Europe Fintech

Kin Score

Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0

Composite quality — 53.5/100 · developing

Contract Quality 14.1 / 19

Developer Ergonomics 7.9 / 15

Access Clarity 7.5 / 15

Operational Transparency 3.6 / 10

Contract Governance 2.6 / 9

Discoverability 5.6 / 8

Regulatory Posture 4.0 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 37/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 9 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Regulatory Posture applies to this provider. Its tags matched the Banking & Open Finance regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/yapily: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 16

Individual APIs this provider publishes, each with its own machine-readable definition.

Yapily Institutions API

Discover and inspect the 2,000+ supported UK and European banks (ASPSPs), including supported features, payment methods, countries, BIC/BBAN identifiers, media assets, and authe...

Yapily Consents and Authorisations API

Create, retrieve, revoke, and re-authorise PSD2 consents for AIS and PIS interactions across UK Open Banking and Berlin Group ASPSPs. Supports redirect, embedded, and decoupled ...

Yapily Payments API (PIS)

Payment Initiation Service Provider (PISP) endpoints for initiating single, scheduled, periodic, bulk, and international payments directly from a customer's bank account. Single...

Yapily Data Plus API

Transaction enrichment endpoints providing merchant detection, MCC categorisation, and spending insights across consumer and business accounts.

Yapily Application Beneficiaries API

Application Beneficiaries Endpoints

Yapily Application Management API

Application Management endpoints help with creating and managing client sub-applications.

Yapily Authorisations API

Before calling [Financial Data](#yapily-api-financial-data) or [Payments](#yapily-api-payments) endpoints, a consent from an end-user must be obtained. Consents are valid for up...

Yapily Constraints API

The constraints endpoints can be used to retrieve institution specific data requirements and rules that will apply when performing other operations.

Yapily Financial Data API

In order to access a user's Financial Data, you are required to request an [Authorisation](#tag/Authorisations) from the user to share the account information the bank has. Once...

Yapily Hosted Consent Pages API

Hosted Consent Pages endpoints for data products

Yapily Hosted Payment Pages API

Hosted Payment Pages endpoints for payments products

Yapily Notifications API

The Notifications endpoints provide an interactive way for user to receive notifications according to different event-types. This feature is currently in private beta. Please re...

Yapily User Beneficiaries API

User Beneficiaries Endpoints

Yapily Users API

The Users endpoints are used to manage each user (otherwise known as the PSU) in Yapily. Each user belongs to an Application and as a consequence, so do each `Consent` created f...

Yapily Variable Recurring Payments API

Variable Recurring Payments enables transfer of money between accounts held by the same person or transfer of money for business payments. In order to make Sweeping Variable Rec...

Yapily Webhooks API

Webhook endpoints

Scroll for all 16

Open Collections 22

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

API Collection

OPEN COLLECTION

Yapily Beneficiaries Application Beneficiaries API

OPEN COLLECTION

Yapily Beneficiaries Application Beneficiaries Application Management API

OPEN COLLECTION

Yapily Beneficiaries Application Beneficiaries Authorisations API

OPEN COLLECTION

Yapily Beneficiaries API

OPEN COLLECTION

Yapily Beneficiaries Application Beneficiaries Consents API

OPEN COLLECTION

Yapily Beneficiaries Application Beneficiaries Constraints API

OPEN COLLECTION

Yapily Data Access API (AIS)

OPEN COLLECTION

Yapily Beneficiaries Application Beneficiaries Data Plus API

OPEN COLLECTION

Yapily Beneficiaries Application Beneficiaries Financial Data API

OPEN COLLECTION

Yapily Beneficiaries Application Beneficiaries Hosted Consent Pages API

OPEN COLLECTION

Yapily Hosted Pages API

OPEN COLLECTION

Yapily Beneficiaries Application Beneficiaries Hosted Payment Pages API

OPEN COLLECTION

Yapily Beneficiaries Application Beneficiaries Institutions API

OPEN COLLECTION

Yapily Beneficiaries Application Beneficiaries Notifications API

OPEN COLLECTION

Yapily Beneficiaries Application Beneficiaries Payments API

OPEN COLLECTION

Yapily Platform API

OPEN COLLECTION

Yapily Beneficiaries Application Beneficiaries User Beneficiaries API

OPEN COLLECTION

Yapily Beneficiaries Application Beneficiaries Users API

OPEN COLLECTION

Yapily Beneficiaries Application Beneficiaries Variable Recurring Payments API

OPEN COLLECTION

Yapily Variable Recurring Payments API

OPEN COLLECTION

Yapily Beneficiaries Application Beneficiaries Webhooks API

OPEN COLLECTION

Scroll for all 22

Pricing Plans 1

Published pricing tiers and plan structures.

Yapily Plans Pricing

6 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Yapily Rate Limits

5 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Yapily Finops

FINOPS

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Yapily Context

40 classes · 1 properties

JSON-LD

Spectral Rules 2

Spectral governance rulesets for linting and validating these APIs.

Yapily API Rules

5 rules · 3 warnings 2 info

SPECTRAL

Yapily API Rules

7 rules · 4 errors 3 warnings

SPECTRAL

JSON Schema 6

Standalone JSON Schema definitions for this provider's data models.

Yapily AccountBalance

5 properties

JSON SCHEMA

Yapily Account

13 properties

JSON SCHEMA

Yapily Consent

20 properties

JSON SCHEMA

Yapily Institution

8 properties

JSON SCHEMA

Yapily PaymentResponse

32 properties

JSON SCHEMA

Yapily Transaction

25 properties

JSON SCHEMA

JSON Structure 2

JSON Structure definitions describing this provider's data shapes.

Yapily Account Structure

0 properties

JSON STRUCTURE

Yapily Payment Structure

0 properties

JSON STRUCTURE

Examples 3

Example request and response payloads for these APIs.

Yapily Create Payment Example

3 fields

EXAMPLE

Yapily Get Account Transactions Example

3 fields

EXAMPLE

Yapily Get Institutions Example

3 fields

EXAMPLE

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Yapily Authentication

http · 1 scheme

SECURITY

Yapily Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Yapily Agentic Access

97 operations · 52 acting · 2 human-in-the-loop

97 operations · 52 acting

AGENTIC

Resources

Get Started 1

Portal, sign-up, and the first successful call

GettingStarted

GettingStarted

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

SpectralRules

SpectralRules

Vocabulary

Vocabulary

Build 9

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

SourceCode

SDKs

SDKs

SDKs

Tools

Tools

Tools

Examples

Scroll for all 9

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Operate 1

Status, limits, changes, and where to get help

RateLimits

RateLimits

Commercial 3

Pricing, plans, and the legal terms of use

Pricing

Pricing

Plans

Plans

FinOps

FinOps

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 1

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Source (apis.yml)

aid: yapily
url: https://raw.githubusercontent.com/api-evangelist/yapily/refs/heads/main/apis.yml
name: Yapily
description: Yapily is a UK-headquartered Open Banking platform that exposes a single REST API across 2,000+ banks in the
  UK and 18+ European countries. The platform provides AISP (Account Information) and PISP (Payment Initiation) capabilities,
  Variable Recurring Payments (VRP), transaction enrichment (Data Plus), Account Validation, and Hosted Payment/Consent Pages.
  Yapily Connect Ltd is FCA-authorised in the UK and Yapily Connect UAB is authorised by the Bank of Lithuania for EU coverage,
  allowing customers to launch without holding their own PSD2 permissions.
deliveryModel:
  model: unknown
  open_source: unknown
  commercial: true
  callable_host: true
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - openapi
  - pricing
  - repository-unlicensed
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: paid
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Paid
  confidence: medium
  source:
  - plans
  - authentication
  - security
  generated: '2026-09-03'
  method: derived
image: https://www.yapily.com/favicon.ico
created: 2026-05-25 00:00:00+00:00
modified: 2026-05-25 00:00:00+00:00
tags:
- Open Banking
- AISP
- PISP
- Payments
- Account Information
- Variable Recurring Payments
- Financial-Services
- PSD2
- FCA
- Berlin Group
- UK
- Europe
- Fintech
tags_raw:
- Open Banking
- AISP
- PISP
- Payments
- Account Information
- Variable Recurring Payments
- Financial Services
- PSD2
- FCA
- Berlin Group
- UK
- Europe
- FinTech
specificationVersion: '0.23'
apis:
- aid: yapily:yapily-institutions-api
  name: Yapily Institutions API
  tags:
  - Institutions
  - ASPSP
  - Open Banking
  tags_raw:
  - Institutions
  - ASPSP
  - Open Banking
  humanURL: https://docs.yapily.com/api/reference/
  baseURL: https://api.yapily.com
  properties:
  - url: https://docs.yapily.com/
    type: Documentation
  - url: openapi/yapily-institutions-api-openapi.yml
    type: OpenAPI
  - url: json-schema/yapily-institution-schema.json
    type: JSONSchema
  - url: examples/yapily-get-institutions-example.json
    type: Examples
  description: Discover and inspect the 2,000+ supported UK and European banks (ASPSPs), including supported features, payment
    methods, countries, BIC/BBAN identifiers, media assets, and authentication mechanisms.
- aid: yapily:yapily-consents-api
  name: Yapily Consents and Authorisations API
  tags:
  - Consents
  - Authorisations
  - PSD2
  - Open Banking
  humanURL: https://docs.yapily.com/api/reference/
  baseURL: https://api.yapily.com
  properties:
  - url: https://docs.yapily.com/
    type: Documentation
  - url: openapi/yapily-consents-api-openapi.yml
    type: OpenAPI
  - url: json-schema/yapily-consent-schema.json
    type: JSONSchema
  description: Create, retrieve, revoke, and re-authorise PSD2 consents for AIS and PIS interactions across UK Open Banking
    and Berlin Group ASPSPs. Supports redirect, embedded, and decoupled flows.
- aid: yapily:yapily-payments-api
  name: Yapily Payments API (PIS)
  tags:
  - Payments
  - PISP
  - Payment Initiation
  - Open Banking
  - PSD2
  humanURL: https://docs.yapily.com/api/reference/
  baseURL: https://api.yapily.com
  properties:
  - url: https://docs.yapily.com/
    type: Documentation
  - url: openapi/yapily-payments-api-openapi.yml
    type: OpenAPI
  - url: json-schema/yapily-payment-response-schema.json
    type: JSONSchema
  - url: json-structure/yapily-payment-structure.json
    type: JSONStructure
  - url: examples/yapily-create-payment-example.json
    type: Examples
  description: Payment Initiation Service Provider (PISP) endpoints for initiating single, scheduled, periodic, bulk, and
    international payments directly from a customer's bank account. Single-use consent per payment.
- aid: yapily:yapily-data-plus-api
  name: Yapily Data Plus API
  tags:
  - Enrichment
  - Categorisation
  - Merchant Detection
  - Insights
  - Open Banking
  humanURL: https://docs.yapily.com/api/reference/
  baseURL: https://api.yapily.com
  properties:
  - url: https://docs.yapily.com/
    type: Documentation
  - url: openapi/yapily-data-plus-api-openapi.yml
    type: OpenAPI
  description: Transaction enrichment endpoints providing merchant detection, MCC categorisation, and spending insights across
    consumer and business accounts.
- aid: yapily:yapily-application-beneficiaries-api
  name: Yapily Application Beneficiaries API
  description: Application Beneficiaries Endpoints
  humanURL: https://docs.yapily.com/api/reference/
  baseURL: https://api.yapily.com
  tags:
  - Application Beneficiaries
  properties:
  - type: OpenAPI
    url: openapi/yapily-application-beneficiaries-api-openapi.yml
  - type: Documentation
    url: https://docs.yapily.com/
  - type: JSONSchema
    url: json-schema/yapily-account-schema.json
  - type: JSONSchema
    url: json-schema/yapily-transaction-schema.json
  - type: JSONSchema
    url: json-schema/yapily-account-balance-schema.json
  - type: JSONStructure
    url: json-structure/yapily-account-structure.json
  - type: JSONLD
    url: json-ld/yapily-context.jsonld
  - type: Examples
    url: examples/yapily-get-account-transactions-example.json
  - type: Documentation
    url: https://docs.yapily.com/payments/vrps/additional-information
- aid: yapily:yapily-application-management-api
  name: Yapily Application Management API
  description: Application Management endpoints help with creating and managing client sub-applications.
  humanURL: https://docs.yapily.com/api/reference/
  baseURL: https://api.yapily.com
  tags:
  - Application Management
  properties:
  - type: OpenAPI
    url: openapi/yapily-application-management-api-openapi.yml
  - type: Documentation
    url: https://docs.yapily.com/
  - type: JSONSchema
    url: json-schema/yapily-account-schema.json
  - type: JSONSchema
    url: json-schema/yapily-transaction-schema.json
  - type: JSONSchema
    url: json-schema/yapily-account-balance-schema.json
  - type: JSONStructure
    url: json-structure/yapily-account-structure.json
  - type: JSONLD
    url: json-ld/yapily-context.jsonld
  - type: Examples
    url: examples/yapily-get-account-transactions-example.json
  - type: Documentation
    url: https://docs.yapily.com/payments/vrps/additional-information
- aid: yapily:yapily-authorisations-api
  name: Yapily Authorisations API
  description: 'Before calling [Financial Data](#yapily-api-financial-data) or [Payments](#yapily-api-payments) endpoints,
    a consent from an end-user must be obtained.


    Consents are valid for up to 90 days for Financial Data endpoints and have a single-use for Payment endpoints i.e. a new
    consent must be obtained for each payment.


    NOTE: A user consent is also referred to as an ''Authorisation''.'
  humanURL: https://docs.yapily.com/api/reference/
  baseURL: https://api.yapily.com
  tags:
  - Authorisations
  properties:
  - type: OpenAPI
    url: openapi/yapily-authorisations-api-openapi.yml
  - type: Documentation
    url: https://docs.yapily.com/
  - type: JSONSchema
    url: json-schema/yapily-account-schema.json
  - type: JSONSchema
    url: json-schema/yapily-transaction-schema.json
  - type: JSONSchema
    url: json-schema/yapily-account-balance-schema.json
  - type: JSONStructure
    url: json-structure/yapily-account-structure.json
  - type: JSONLD
    url: json-ld/yapily-context.jsonld
  - type: Examples
    url: examples/yapily-get-account-transactions-example.json
  - type: Documentation
    url: https://docs.yapily.com/payments/vrps/additional-information
- aid: yapily:yapily-constraints-api
  name: Yapily Constraints API
  description: The constraints endpoints can be used to retrieve institution specific data requirements and rules that will
    apply when performing other operations.
  humanURL: https://docs.yapily.com/api/reference/
  baseURL: https://api.yapily.com
  tags:
  - Constraints
  properties:
  - type: OpenAPI
    url: openapi/yapily-constraints-api-openapi.yml
  - type: Documentation
    url: https://docs.yapily.com/
  - type: JSONSchema
    url: json-schema/yapily-account-schema.json
  - type: JSONSchema
    url: json-schema/yapily-transaction-schema.json
  - type: JSONSchema
    url: json-schema/yapily-account-balance-schema.json
  - type: JSONStructure
    url: json-structure/yapily-account-structure.json
  - type: JSONLD
    url: json-ld/yapily-context.jsonld
  - type: Examples
    url: examples/yapily-get-account-transactions-example.json
  - type: Documentation
    url: https://docs.yapily.com/payments/vrps/additional-information
- aid: yapily:yapily-financial-data-api
  name: Yapily Financial Data API
  description: In order to access a user's Financial Data, you are required to request an [Authorisation](#tag/Authorisations)
    from the user to share the account information the bank has. Once a `consent-token` is obtained, you can call the necessary
    Financial Data endpoint(s) to retrieve the user's data.
  humanURL: https://docs.yapily.com/api/reference/
  baseURL: https://api.yapily.com
  tags:
  - Financial Data
  properties:
  - type: OpenAPI
    url: openapi/yapily-financial-data-api-openapi.yml
  - type: Documentation
    url: https://docs.yapily.com/
  - type: JSONSchema
    url: json-schema/yapily-account-schema.json
  - type: JSONSchema
    url: json-schema/yapily-transaction-schema.json
  - type: JSONSchema
    url: json-schema/yapily-account-balance-schema.json
  - type: JSONStructure
    url: json-structure/yapily-account-structure.json
  - type: JSONLD
    url: json-ld/yapily-context.jsonld
  - type: Examples
    url: examples/yapily-get-account-transactions-example.json
  - type: Documentation
    url: https://docs.yapily.com/payments/vrps/additional-information
- aid: yapily:yapily-hosted-consent-pages-api
  name: Yapily Hosted Consent Pages API
  description: Hosted Consent Pages endpoints for data products
  humanURL: https://docs.yapily.com/api/reference/
  baseURL: https://api.yapily.com
  tags:
  - Hosted Consent Pages
  properties:
  - type: OpenAPI
    url: openapi/yapily-hosted-consent-pages-api-openapi.yml
  - type: Documentation
    url: https://docs.yapily.com/
  - type: JSONSchema
    url: json-schema/yapily-account-schema.json
  - type: JSONSchema
    url: json-schema/yapily-transaction-schema.json
  - type: JSONSchema
    url: json-schema/yapily-account-balance-schema.json
  - type: JSONStructure
    url: json-structure/yapily-account-structure.json
  - type: JSONLD
    url: json-ld/yapily-context.jsonld
  - type: Examples
    url: examples/yapily-get-account-transactions-example.json
  - type: Documentation
    url: https://docs.yapily.com/payments/vrps/additional-information
- aid: yapily:yapily-hosted-payment-pages-api
  name: Yapily Hosted Payment Pages API
  description: Hosted Payment Pages endpoints for payments products
  humanURL: https://docs.yapily.com/api/reference/
  baseURL: https://api.yapily.com
  tags:
  - Hosted Payment Pages
  properties:
  - type: OpenAPI
    url: openapi/yapily-hosted-payment-pages-api-openapi.yml
  - type: Documentation
    url: https://docs.yapily.com/
  - type: JSONSchema
    url: json-schema/yapily-account-schema.json
  - type: JSONSchema
    url: json-schema/yapily-transaction-schema.json
  - type: JSONSchema
    url: json-schema/yapily-account-balance-schema.json
  - type: JSONStructure
    url: json-structure/yapily-account-structure.json
  - type: JSONLD
    url: json-ld/yapily-context.jsonld
  - type: Examples
    url: examples/yapily-get-account-transactions-example.json
  - type: Documentation
    url: https://docs.yapily.com/payments/vrps/additional-information
- aid: yapily:yapily-notifications-api
  name: Yapily Notifications API
  description: The Notifications endpoints provide an interactive way for user to receive notifications according to different
    event-types. This feature is currently in private beta. Please reach out if you require access.
  humanURL: https://docs.yapily.com/api/reference/
  baseURL: https://api.yapily.com
  tags:
  - Notification
  tags_raw:
  - Notifications
  properties:
  - type: OpenAPI
    url: openapi/yapily-notifications-api-openapi.yml
  - type: Documentation
    url: https://docs.yapily.com/
  - type: JSONSchema
    url: json-schema/yapily-account-schema.json
  - type: JSONSchema
    url: json-schema/yapily-transaction-schema.json
  - type: JSONSchema
    url: json-schema/yapily-account-balance-schema.json
  - type: JSONStructure
    url: json-structure/yapily-account-structure.json
  - type: JSONLD
    url: json-ld/yapily-context.jsonld
  - type: Examples
    url: examples/yapily-get-account-transactions-example.json
  - type: Documentation
    url: https://docs.yapily.com/payments/vrps/additional-information
- aid: yapily:yapily-user-beneficiaries-api
  name: Yapily User Beneficiaries API
  description: User Beneficiaries Endpoints
  humanURL: https://docs.yapily.com/api/reference/
  baseURL: https://api.yapily.com
  tags:
  - User Beneficiaries
  properties:
  - type: OpenAPI
    url: openapi/yapily-user-beneficiaries-api-openapi.yml
  - type: Documentation
    url: https://docs.yapily.com/
  - type: JSONSchema
    url: json-schema/yapily-account-schema.json
  - type: JSONSchema
    url: json-schema/yapily-transaction-schema.json
  - type: JSONSchema
    url: json-schema/yapily-account-balance-schema.json
  - type: JSONStructure
    url: json-structure/yapily-account-structure.json
  - type: JSONLD
    url: json-ld/yapily-context.jsonld
  - type: Examples
    url: examples/yapily-get-account-transactions-example.json
  - type: Documentation
    url: https://docs.yapily.com/payments/vrps/additional-information
- aid: yapily:yapily-users-api
  name: Yapily Users API
  description: The Users endpoints are used to manage each user (otherwise known as the PSU) in Yapily. Each user belongs
    to an Application and as a consequence, so do each `Consent` created for a particular `User`.
  humanURL: https://docs.yapily.com/api/reference/
  baseURL: https://api.yapily.com
  tags:
  - User
  tags_raw:
  - Users
  properties:
  - type: OpenAPI
    url: openapi/yapily-users-api-openapi.yml
  - type: Documentation
    url: https://docs.yapily.com/
  - type: JSONSchema
    url: json-schema/yapily-account-schema.json
  - type: JSONSchema
    url: json-schema/yapily-transaction-schema.json
  - type: JSONSchema
    url: json-schema/yapily-account-balance-schema.json
  - type: JSONStructure
    url: json-structure/yapily-account-structure.json
  - type: JSONLD
    url: json-ld/yapily-context.jsonld
  - type: Examples
    url: examples/yapily-get-account-transactions-example.json
  - type: Documentation
    url: https://docs.yapily.com/payments/vrps/additional-information
- aid: yapily:yapily-variable-recurring-payments-api
  name: Yapily Variable Recurring Payments API
  description: "Variable Recurring Payments enables transfer of money between accounts held by the same person or transfer\
    \ of money for business payments. \n\nIn order to make Sweeping Variable Recurring Payments on behalf of a user, you are\
    \ required to request an [Consent](#tag/Authorisations) from the user by calling the Sweeping Consent endpoint to authorise\
    \ the user's account to make the payment. Once a `consent-token` is obtained, you can call the Payments endpoint to execute\
    \ the Sweeping Variable Recurring Payments transaction. Before executing the payment, you have the option to confirm availability\
    \ of funds in the user's account by calling the Funds Confirmation endpoint. \n\nSee [VRP Payments](/payments/vrps/additional-information)\
    \ for more information."
  humanURL: https://docs.yapily.com/api/reference/
  baseURL: https://api.yapily.com
  tags:
  - Variable Recurring Payments
  properties:
  - type: OpenAPI
    url: openapi/yapily-variable-recurring-payments-api-openapi.yml
  - type: Documentation
    url: https://docs.yapily.com/
  - type: JSONSchema
    url: json-schema/yapily-account-schema.json
  - type: JSONSchema
    url: json-schema/yapily-transaction-schema.json
  - type: JSONSchema
    url: json-schema/yapily-account-balance-schema.json
  - type: JSONStructure
    url: json-structure/yapily-account-structure.json
  - type: JSONLD
    url: json-ld/yapily-context.jsonld
  - type: Examples
    url: examples/yapily-get-account-transactions-example.json
  - type: Documentation
    url: https://docs.yapily.com/payments/vrps/additional-information
- aid: yapily:yapily-webhooks-api
  name: Yapily Webhooks API
  description: Webhook endpoints
  humanURL: https://docs.yapily.com/api/reference/
  baseURL: https://api.yapily.com
  tags:
  - Webhook
  tags_raw:
  - Webhooks
  properties:
  - type: OpenAPI
    url: openapi/yapily-webhooks-api-openapi.yml
  - type: Documentation
    url: https://docs.yapily.com/
  - type: JSONSchema
    url: json-schema/yapily-account-schema.json
  - type: JSONSchema
    url: json-schema/yapily-transaction-schema.json
  - type: JSONSchema
    url: json-schema/yapily-account-balance-schema.json
  - type: JSONStructure
    url: json-structure/yapily-account-structure.json
  - type: JSONLD
    url: json-ld/yapily-context.jsonld
  - type: Examples
    url: examples/yapily-get-account-transactions-example.json
  - type: Documentation
    url: https://docs.yapily.com/payments/vrps/additional-information
common:
- type: CapabilityMap
  url: capabilities/yapily-capability-edges.yml
  name: Yapily Business Capability Map
- type: AgenticAccess
  url: agentic-access/yapily-agentic-access.yml
- type: DomainSecurity
  url: security/yapily-domain-security.yml
- type: Authentication
  url: authentication/yapily-authentication.yml
- url: https://www.yapily.com/
  type: Website
- url: https://docs.yapily.com/
  type: Documentation
- url: https://docs.yapily.com/getting-started/overview
  type: GettingStarted
- url: https://github.com/yapily
  type: GitHubOrganization
- url: https://github.com/yapily/yapily-openapi
  type: SourceCode
- url: https://github.com/yapily/yapily-sdk-java
  type: SDKs
- url: https://github.com/yapily/yapily-sdk-python
  type: SDKs
- url: https://github.com/yapily/yapily-sdk-nodejs
  type: SDKs
- url: https://github.com/yapily/helm-charts
  type: Tools
- url: https://github.com/yapily/yapily-mulesoft-connector
  type: Tools
- url: https://github.com/yapily/registration-scripts
  type: Tools
- url: https://github.com/yapily/yapily-demo-pisp-flutter
  type: Examples
- url: https://www.yapily.com/pricing
  type: Pricing
- url: plans/yapily-plans-pricing.yml
  type: Plans
- url: rate-limits/yapily-rate-limits.yml
  type: RateLimits
- url: finops/yapily-finops.yml
  type: FinOps
- url: rules/yapily-rules.yml
  type: SpectralRules
- url: vocabulary/yapily-vocabulary.yml
  type: Vocabulary
- url: https://www.yapily.com/blog
  type: Blog
solutions:
- name: Account-to-Account Checkout
  description: Replace card rails with PISP-initiated A2A payments at checkout using single payments or Pay By Link.
- name: Subscription Billing via VRP
  description: Replace card-on-file with Variable Recurring Payments for commercial subscriptions, with consent-bound caps.
- name: Affordability and Underwriting
  description: Use AIS plus Data Plus enrichment to score affordability for lending, BNPL, and rentals.
- name: Personal Finance Management
  description: Power PFM apps with consented bank data across 19 European markets through a single API.
- name: Treasury and Reconciliation
  description: Pull balances and transactions across multiple business accounts for cash management and reconciliation.
- name: Account Ownership Validation
  description: Verify customer-provided bank details at onboarding using Yapily Validate.
integrations:
- name: UK Open Banking
  description: Connects to UK Open Banking Standard ASPSPs (CMA9 plus long tail) under FCA regulation.
- name: Berlin Group NextGenPSD2
  description: Connects to EU ASPSPs implementing the Berlin Group NextGenPSD2 spec.
- name: Yapily Connect (FCA)
  description: Yapily Connect Ltd acts as the regulated AISP/PISP of record in the UK.
- name: Yapily Connect (Bank of Lithuania)
  description: Yapily Connect UAB acts as the regulated AISP/PISP of record across the EU.
- name: MuleSoft
  description: yapily-mulesoft-connector enables drag-and-drop integration in MuleSoft.
- name: Java / Python / Node.js SDKs
  description: Official SDKs published from the canonical OpenAPI spec.
- name: Kubernetes (Helm)
  description: helm-charts repo for deploying Yapily-adjacent workloads.
useCases:
- name: Pay-ins for Marketplaces
- name: Bill Payments and Direct-to-Account Refunds
- name: Salary Advance and Income Verification
- name: Wealth and Investment Funding
- name: Charity Donations
- name: Bureaux de Change and FX Onboarding
- name: Bulk Payouts (Payroll, Supplier Payments)
- name: B2B Sweeping (Cash Concentration)
maintainers:
- FN: Kin Lane
  email: info@apievangelist.com

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/yapily"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/yapily/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/yapily/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.