integrations.sh
← all integrations

OpenFinTech.io

OpenAPI apis-guru financial

Introduction

is an open database that comprises of standardized primary data for FinTech industry.
It contains such information as geolocation data (countries, cities, regions), organizations, currencies (national, digital, virtual, crypto), banks, digital exchangers, payment providers (PSP), payment methods, etc.
It is created for communication of cross-integrated micro-services on "one language". This is achieved through standardization of entity identifiers that are used to exchange information among different services.

UML

UML Domain Model diagram you can find .

Persistence

Entities are updated not more than 1 time per day.

Terms and Conditions

This OpenFinTech.io is made available under the .
Any rights in individual contents of the database are licensed under the .

Contacts

For any questions, please email -
Or you can contact us at

Powered by

Get Started

If you use or similar program which can operate with swagger`s files - just our spec and . Also you can try live .

Overview

The OpenFinTech API is organized around . Our API has predictable, resource-oriented URLs, and uses HTTP response codes to indicate API errors.
API is based on standard. JSON is returned by all API responses, including errors, although our API libraries convert responses to appropriate language-specific objects.
JSON API requires use of the JSON API media type (application/vnd.api+json) for exchanging data.

Additional Request Headers

ACCEPT HEADER

Your requests should always include the header:

curl
Accept: application/vnd.api+json

Authentication

To use OpenFinTech API no needed authorization.

Versioning

When we make changes to the API, we release new, dated versions. The current version is 2017-08-24. Read our API upgrades guide [blocked] to see our API changelog and to learn more about backwards compatibility.

Pagination

OpenFinTech APIs to retrieve lists of banks, currencies and other resources - paginated to 100 items by default. The pagination information will be included in the list API response under the node name meta - contains information about listed objects [total - contains information about total count of listed objects, pages - count of pages], links - contain links to navigate between pages [first - link to first page, prev - link to previous page, next - link to next page, last - link to last page].
By default first page will be listed. For navigating through pages, use the page parameter (e.g. page[number], page[size]).
The page[size] parameter can be used to set the number of records that you want to receive in the response.
The page[number] parameter can be used to set needed page number.
Example of response:

json
{  "meta": {    "total": 419,    "pages": 42  },  "links": {    "first": "/v1/{path}?page[number]=1&page[size]=10",    "prev": "/v1/{path}?page[number]=39&page[size]=10",    "next": "/v1/{path}?page[number]=41&page[size]=10",    "last": "/v1/{path}?page[number]=42&page[size]=10"  }

Sorting

OpenFinTech`s API supported query parameter to sort result collection [e.g. ?sort=code]. Information about available parameters may be found in the endpoint description. Positive parameter [e.g. ?sort=code] points to ascending sorting, negative [e.g. ?sort=-code] - to descending sorting. Also, supported multiple sorting parameters [e.g. ?sort=code, -name, id, etc.]

curl
https://api.openfintech.io/v1/countries?sort=name,-area

Filtering

Filtering provided by unique query key filter[*filtering_condition*]. Information about available parameters may be found in the endpoint description.

curl
https://api.openfintech.io/v1/countries?filter[region]=europe

Images

OpenFinTech provides two types of images: icons and logos. To get one of those types you should to use next url pattern:

curl
https://api.openfintech.io/v1/{path}/{id}/{icon/logo}

Also, images can be resized by adding next parameters: h={height}&w={width}. For example, you want to get organization icon with width equals to 20 pixels:

curl
https://api.openfintech.io/v1/organizations/{id}/icon?w=20&h=20

If argument height or width is missing API returns original image with real sizes.

Errors

API uses conventional HTTP response codes to indicate the success or failure of an API request. In general, codes in the 2xx range indicate success, codes in the 4xx range indicate an error that failed given the information provided (e.g., a required parameter was omitted, etc.), and codes in the 5xx range indicate an error with OpenFinTech's servers (these are rare).

CodeDescription
200 - OKEverything worked as expected.
400 - Bad RequestThe request was unacceptable, often due to missing a required parameter.
401 - UnauthorizedNo valid API key provided.
402 - Request FailedThe parameters were valid but the request failed.
404 - Not FoundThe requested resource doesn't exist.
409 - ConflictThe request conflicts with another request (perhaps due to using the same idempotent key).
429 - Too Many RequestsToo many requests hit the API too quickly. We recommend an exponential backoff of your requests.
500, 502, 503, 504 - Server ErrorsSomething went wrong on OpenFinTech's end. (These are rare.)
`
Homepage
https://api.apis.guru/v2/specs/openfintech.io/2017-08-24.json
Provider
openfintech.io
OpenAPI version
2.0
Spec (JSON)
https://api.apis.guru/v2/specs/openfintech.io/2017-08-24/swagger.json
Spec (YAML)
https://api.apis.guru/v2/specs/openfintech.io/2017-08-24/swagger.yaml

Tool extraction failed: Only OpenAPI 3.x documents are supported. Swagger 2.x documents should be converted first..