Affinis Data APIs Overview
From ISO 20022 to Identity to Trade Data
Identity APIs
Legal Entity Identifiers
Legal Entity Identifiers (LEIs) are unique codes to identify an organisation. Our API endpoints enable verification of an LEI, getting the LEI details, getting any BICs and for a given BIC, getting any LEIs.
Endpoints to:
- Get all LEIs for a given BIC
- Get the complete organisation information for a given LEI
- Get all BICs for a given LEI
- Validate a given LEI (syntax and checksum)
Documentation can be found here.
A generic example to find all LEIs for a BIC:
- https://api.affinis.co.uk/v1/identity/leis/{bic}/lei
A specific example for the BIC BCITITMMXXX would be:
-
- https://api.affinis.co.uk/v1/identity/leis/BCITITMMXXX/lei
ISO 20022 APIs
Payments and Reports
Developing your bank’s own payment initiation API or want to generate test statements and reports? Want to see a full pain.001.001.09 model? This demonstration API has endpoints for a payment initiation and generates sample camt.053, camt.052 and camt.054, conforming to current ISO 20022 standards (CBPR+ usage guidelines). Contact us for more information on all matters related to ISO 20022.
This POST endpoint shows a full ISO 20022 payment initiation (pain.001.001.09) model. Posting a pain.001 message will trigger a pain.002.001.10 status response which echoes back the Payment Information message IDs and the Customer Credit Transfer Initiation message IDs, including the End-To-End ID, UETR etc.
Documentation can be found here.
Contact us for more information on all matters related to ISO 20022.
This GET endpoint will allow you to generate an example ISO 20022 statement. This will be in XML as a camt.053.001.08 which complies with Swift CBPR+ usage guidelines (standards release 2023). Enter dummy account number, currency, opening balance and set the number of Entry items and whether to include structured remittance information. For structured remittance information, if included, one item will be generated for each Entry.
You can also enter the message recipient and account owner (organisation IDs such as BIC, LEI or other ID) for use cases where these differ.
Documentation can be found here.
A generic example to generate a statement for a given account number would be:
- https://api.affinis.co.uk/v1/iso20022/cashmanagement/statement/{account}?currency=EUR
A specific example for the account number 123456789 would be:
- https://api.affinis.co.uk/v1/iso20022/cashmanagement/statement/123456789?currency=EUR&openingbalance=250&entryitems=6&remittanceinfo=true
This GET endpoint will allow you to generate an example ISO 20022 account report. This will be in XML as a camt.052.001.08 which complies with Swift CBPR+ usage guidelines (standards release 2023). Enter dummy account number, currency, opening balance and set the number of Entry items and whether to include balances (recommended) and structured remittance information. For structured remittance information, if included, one item will be generated for each Entry. You can also enter the message recipient and account owner (organisation IDs such as BIC, LEI or other ID) for use cases where these differ.
This is effectively an intra-day statement and this sample will simulate the previous 1 hour period.
Documentation can be found here.
A generic example to generate a statement for a given account number would be:
- https://api.affinis.co.uk/v1/iso20022/cashmanagement/report/{account}?currency=EUR
A specific example for the account number 123456789 would be:
- https://api.affinis.co.uk/v1/iso20022/cashmanagement/report/123456789?currency=EUR&openingbalance=250&balance=true&entryitems=6&remittanceinfo=true
This GET endpoint will allow you to generate an example ISO 20022 debit/credit notification. This will be in XML as a camt.054.001.08 which complies with Swift CBPR+ usage guidelines (standards release 2023). Enter dummy account number, currency and set the number of Entry items and whether to include structured remittance information. For structured remittance information, if included, one item will be generated for each Entry.
You can also enter the message recipient and account owner (organisation IDs such as BIC, LEI or other ID) for use cases where these differ.
Documentation can be found here.
A generic example to generate a statement for a given account number would be:
- https://api.affinis.co.uk/v1/iso20022/cashmanagement/notification/{account}?currency=EUR
A specific example for the account number 123456789 would be:
- https://api.affinis.co.uk/v1/iso20022/cashmanagement/notification/123456789?currency=EUR&entryitems=6&remittanceinfo=true
Trade Data APIs
OHLCV Data
Having difficulty finding historical candlestick data for crypto assests? We have an API for OHLCV (candlestick) data with technical indicators for a range of crypto trading pairs.
This data comes from the Kraken exchange. Get OHLCV data with technical indicators for a range of crypto trading pairs. Data is available for 5, 15, 30 and 60 minute intervals. By default, 48 periods of the specified interval are returned for the window of data.
Documentation can be found here.
A generic example:
- https://api.affinis.co.uk/v1/trade/ohlcv/{pair}?interval=60&window=48
A specific example for Bitcoin/GBP for 60 mins intervals for 24 hour window would be:
- https://api.affinis.co.uk/v1/trade/ohlcv/XXBTZGBP?interval=60&window=24
