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

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 a `consent-token` is obtained, you can call the necessary Financial Data endpoint(s) to retrieve the user's data.

Yapily Financial Data API is one of 16 APIs that Yapily publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 4 JSON Schema definitions.

Tagged areas include Financial Data. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, and 4 JSON Schemas.

This API exposes 13 operations across 13 paths, and defines 84 schemas. It is described by OpenAPI 3.2.0, at version 12.4.0.

Requests are made against a single base URL, https://api.yapily.com.

13 operations 13 paths 84 schemas 13 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
12.4.0
Base URL
https://api.yapily.com
Authentication
HTTP Basic
Resource Areas
1

Authentication & Security 1

Yapily Financial Data API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (basicAuth). By default, every request must be authenticated.

  • basicAuth — Use HTTP Basic Authentication with your Application ID as username and Application Secret as password. Manage credentials in the [Yapily Console](https://conso…

Paths & Operations 13

Across 13 paths, the API surfaces 13 operations — 13 GET. Each is listed below with its method, path, parameters, and response codes.

Financial Data 13

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…

GET
/accounts
Get Accounts
getAccounts 5 params → 200default
GET
/accounts/{accountId}
Get Account
getAccount 6 params → 200default
GET
/accounts/{accountId}/balances
Get Account Balances
getAccountBalances 6 params → 200default
GET
/accounts/{accountId}/beneficiaries
Get Account Beneficiaries
getBeneficiaries 3 params → 200default
GET
/accounts/{accountId}/direct-debits
Get Account Direct Debits
getAccountDirectDebits 4 params → 200default
GET
/accounts/{accountId}/periodic-payments
Get Account Periodic Payments
getAccountPeriodicPayments 4 params → 200default
GET
/accounts/{accountId}/scheduled-payments
Get Account Scheduled Payments
getAccountScheduledPayments 4 params → 200default
GET
/accounts/{accountId}/statements
Get Account Statements
getStatements 8 params → 200default
GET
/accounts/{accountId}/statements/{statementId}
Get Account Statement
getStatement 4 params → 200default
GET
/accounts/{accountId}/statements/{statementId}/file
Get Account Statement File
getStatementFile 4 params → 200default
GET
/accounts/{accountId}/transactions
Get Account Transactions
getTransactions 12 params → 200default
GET
/identity
Get Identity
getIdentity 2 params → 200default
GET
/accounts/{accountId}/real-time/transactions
Get Real Time Account Transactions
getRealTimeTransactions 9 params → 200401default

Schemas 84

The contract defines 84 schemas that model the data the API accepts and returns. The most detailed are PaymentResponse (32 properties), Transaction (25 properties), RealTimeTransaction (21 properties), Account (13 properties). Each schema is shown below with its type and property counts.

Categorisation
object
Income and Expense categorisation that the Yapily categorisation engine has determined for the transaction.
2 properties
FilteredClientPayloadListPaymentResponse
object
6 properties
PaymentStatus
string
The status of the Payment. For more information, see [Payment Status](/guides/payments/payment-status/)
Account
object
13 properties
TransactionChargeDetails
object
Details the charges that will apply to the transaction.
1 property
ApiListResponseOfDirectDebitResponse
object
7 properties
BeneficiaryPayee
object
Mandatory. Account details belonging to the Beneficiary Payee (person/ business). You must define this in your payment request along with all of the nested man…
3 properties 1 required
RefundAccount
object
The account to which funds should be returned if the payment is to be later refunded.
2 properties
ApiResponseOfIdentity
object
6 properties
AccountName
object
1 property
ResponseMeta
object
1 property
Address
object
Conditional. The address of the Payee or Payer. - payee.address is mandatory when the paymentType is an INTERNATIONAL payment - An Institution may require you…
10 properties
ConsolidatedAccountInformation
object
Summary information regarding account balances of the overall account provided by the bank
2 properties
ApiResponseOfBalances
object
6 properties
Enrichment
object
Enriched data that has been derived by Yapily using it's data processing and machine learning techniques.
7 properties
ApiResponseOfAccountStatement
object
6 properties
PaymentIsoStatus
object
The payment status code, as denoted by a 3-letter ISO 20022 code.
2 properties
IsoBankTransactionCode
object
Defines the underlying transaction type (e.g. Card or Debit Transactions, Loans or Mortages). Conforms to ISO standards - ISO 20022.
3 properties
FilteredClientPayloadListTransaction
object
6 properties
Pagination
object
3 properties
AccountIdentification
object
2 properties 2 required
CreditLineType
string
Mandatory. The type of credit that has been provided.
TransactionBalance
object
2 properties
ApiListResponseOfRealTimeTransaction
object
6 properties
FilteredClientPayloadListDirectDebitResponse
object
6 properties
CurrencyExchange
object
Provides details on the currrency exchange.
4 properties
AddressDetails
object
1 property
PaymentResponse
object
32 properties
AccountIdentificationType
string
Mandatory. Used to describe the format of the account. See [Account Identification Combinations](/payments/payment-resources/intro-to-payment-executionaccount-…
IdentityAddress
object
8 properties
MultiAuthorisation
object
Details the additional levels of authorisation which are required from, and being managed by, the Institution.
5 properties
ResponseListMeta
object
3 properties
ApiError
object
Provides details of the error that has occurred.
6 properties
Amount
object
Mandatory. Monetary Amount.
2 properties 2 required
Payee
object
Mandatory. Details of the beneficiary [person or business].
6 properties 2 required
FilterAndSort
object
6 properties
FilteredClientPayloadListAccountStatement
object
6 properties
AddressTypeEnum
string
Optional. The type of address
StatementReference
object
Unique reference for a statement period. This may be optionally populated if available.
1 property
Payer
object
Conditional. Details of the benefactor [person or business].
3 properties 1 required
PriorityCodeEnum
string
Transaction
object
Details of a transaction (credit or debit) that has occurred on the account.
25 properties
RawResponse
object
[DEPRECATED] Interaction (raw request and response) that occurred with the Institution in order to fulfil a request.
5 properties
AccountBalanceType
string
Specifies the type of the stated account balance.
Identity
object
Identification details of a party associated with an account e.g. (account owner or operator).
9 properties
UsageType
string
The customer segment of the account.
Merchant
object
Details of the merchant involved in the transaction.
2 properties
ApiCall
object
ResponseMetaWithCount
object
2 properties
Balances
object
2 properties
ApiListResponseOfPaymentResponse
object
7 properties
ProprietaryBankTransactionCode
object
Transaction code that is proprietary to the Institution.
2 properties
FrequencyResponse
object
Mandatory. Defines the intervals at which payment should be made.
4 properties
PaymentChargeDetails
object
Details the charges that will apply to the payment.
3 properties
ApiResponseError
object
Used to return errors from the bank from each request - 400 - Returned by any POST endpoint when the body does not conform to the contract - 401 - Returned by…
2 properties
TransactionStatusEnum
string
DirectDebitResponse
object
6 properties
PayeeAccountType
string
Optional. The payee account type. Allowed values: BUSINESS, BUSINESSSAVING, CHARITY, COLLECTION, CORPORATE, EWALLET, GOVERNMENT, INVESTMENT, INVESTMENTISA, JOI…
EnrichmentMerchant
object
Details of the merchant, identified by Yapily data services.
2 properties
CreditLine
object
Mandatory. Details whether the account has access to a credit line from an Institution.
2 properties
FilteredClientPayloadListAccount
object
6 properties
InstitutionError
object
Raw error details provided by the Institution, when it was the error source.
2 properties
RealTimeTransaction
object
21 properties
IsoCodeDetails
object
Mandatory. Details the identification of the ISO code.
2 properties
Beneficiary
object
Account information belonging to the target beneficiary (person/ business).
4 properties
ApiListResponseOfAccountStatement
object
7 properties
ExchangeRateInformationResponse
object
5 properties 2 required
ApiListResponseOfTransaction
object
7 properties
PaymentStatusDetails
object
6 properties
DirectDebitPayee
object
1 property
RawRequest
object
8 properties
RateTypeEnum
string
Mandatory. The type used to complete the currency exchange.
AccountType
string
The type of account e.g. (Credit Card, Savings).
ApiResponseOfAccount
object
6 properties
PaymentIsoStatusCodeEnum
string
The ISO 20022 PaymentStatusCode.
Next
object
4 properties
ApiListResponseOfBeneficiary
object
6 properties
SortEnum
string
The attribute on which resources / records returned should be sorted. Valid options for the sort parameter.
AccountApiListResponse
object
7 properties
FrequencyEnumExtended
string
Mandatory. See [payment frequency](/guides/payments/payment-execution/periodic-payments/payment-frequency) for more information
TransactionHash
object
An unique identifier for the transaction that was generated by Yapily. This is a hash of transaction attributes and may be useful an id is not present (and the…
1 property
AccountStatement
object
Statement information belonging to the account.
4 properties
AccountBalance
object
5 properties
ResponseForwardedData
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

yapily-financial-data-api-openapi.yml Raw ↑

Other APIs Yapily publishes across the network.

Yapily Institutions API
Yapily Consents and Authorisations API
Yapily Payments API (PIS)
Yapily Data Plus API
Yapily Application Beneficiaries API
Yapily Application Management API
Yapily Authorisations API
Yapily Constraints API
Yapily Hosted Consent Pages API
Yapily Hosted Payment Pages API
Yapily Notifications API
Yapily User Beneficiaries API
Where this information came from

This is an independent, third-party profile of Yapily Financial Data 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.