TB Accounts 1.0.1

Download OpenAPI 2.0 specification (swagger)

To play with our API you should setup Authentication to Sandbox URI.

API URL : https://api.tatrabanka.sk/sandbox/api/v1

API Key

API Key: No API key is available.
- Toggle All

/accounts

Show/Hide
List Operations
Expand Operations

GET /accounts

getAccounts

Implementation Notes

The operation provides the relevant data about bank customer's accounts in form of a list.

Parameters

Parameter	Value	Description
Request-ID		Request-ID An unique identifier of a particular request message. Although it may be arbitrary string, it is strongly recommended to use a Universally Unique Ifentifier (UUID) version 4 form (RFC4122 https://tools.ietf.org/html/rfc4122).
Correlation-ID		Correlation-ID An unique correlation identifier correlates the request and the response messages as a pair especially useful for audit logs. Although it may be arbitrary string, it is strongly recommended to use a Universally Unique Ifentifier (UUID) version 4 form (RFC4122 https://tools.ietf.org/html/rfc4122).
Process-ID		Process-ID Identifier of a business or technical process to what the set of requests and response pairs are organized. Although it may be arbitrary string, it is strongly recommended to use a Universally Unique Ifentifier (UUID) version 4 form (RFC4122 https://tools.ietf.org/html/rfc4122).
PSU-IP-Address		PSU-IP-Address Identifier of a customer's IP address from which he/she is connected to the TPP infrastructure. It might be in the format of IPv4 o IPv6 address.
PSU-Device-OS		PSU-Device-OS A customer's device and/or operating system identification from which he/she is connected to the TPP infrastructure.
PSU-User-Agent		PSU-User-Agent A customer's web browser of other client device identification from which he/she is connected to the TPP infrastructure.
PSU-Geo-Location		PSU-Geo-Location The GPS coordinates of the current customer's location in the moment of connection to the TPP infrastructure.
pageSize		pageSize The number of records included in one page for displaying.
pageCount		pageCount The total number of pages of determined size within the defined date range.
page		page The sequence number of a page in regards to page size for a record set. Because it starts at number 1, it should be considered as an offset from the beginning from a page set.
order		order The direction of sorting records in a page.

Response Messages

HTTP Status Code	Reason	Response Model
200
400	The request could not be understood by the bank server due to malformed syntax. Your application should not repeat the request without modifications.
401	The request requires user authentication.
403	The bank server understood the request, but is refusing to fulfill it. Authorization will not help and the request should not be repeated.
500	The bank server encountered an unexpected condition which prevented it from fulfilling the request.
503	The bank server is currently unable to handle the request due to maintenance of the server.

POST /accounts/information

postAccountInfo

Implementation Notes

The operation provides the relevant data from a bank customer's account identified by IBAN. Only AISP is allowed to use current operation.

Parameters

Parameter	Value	Description
Request-ID		Request-ID An unique identifier of a particular request message. Although it may be arbitrary string, it is strongly recommended to use a Universally Unique Ifentifier (UUID) version 4 form (RFC4122 https://tools.ietf.org/html/rfc4122).
Correlation-ID		Correlation-ID An unique correlation identifier correlates the request and the response messages as a pair especially useful for audit logs. Although it may be arbitrary string, it is strongly recommended to use a Universally Unique Ifentifier (UUID) version 4 form (RFC4122 https://tools.ietf.org/html/rfc4122).
Process-ID		Process-ID Identifier of a business or technical process to what the set of requests and response pairs are organized. Although it may be arbitrary string, it is strongly recommended to use a Universally Unique Ifentifier (UUID) version 4 form (RFC4122 https://tools.ietf.org/html/rfc4122).
PSU-IP-Address		PSU-IP-Address Identifier of a customer's IP address from which he/she is connected to the TPP infrastructure. It might be in the format of IPv4 o IPv6 address.
PSU-Device-OS		PSU-Device-OS A customer's device and/or operating system identification from which he/she is connected to the TPP infrastructure.
PSU-User-Agent		PSU-User-Agent A customer's web browser of other client device identification from which he/she is connected to the TPP infrastructure.
PSU-Geo-Location		PSU-Geo-Location The GPS coordinates of the current customer's location in the moment of connection to the TPP infrastructure.

Response Messages

HTTP Status Code	Reason	Response Model
201
400	The request could not be understood by the bank server due to malformed syntax. Your application should not repeat the request without modifications.
401	The request requires user authentication.
403	The bank server understood the request, but is refusing to fulfill it. Authorization will not help and the request should not be repeated.
500	The bank server encountered an unexpected condition which prevented it from fulfilling the request.
503	The bank server is currently unable to handle the request due to maintenance of the server.

POST /accounts/transactions

postTransactions

Implementation Notes

The list of financial transactions perfomed on a customer's bank account withing a date period.

Parameters

Parameter	Value	Description
Request-ID		Request-ID An unique identifier of a particular request message. Although it may be arbitrary string, it is strongly recommended to use a Universally Unique Ifentifier (UUID) version 4 form (RFC4122 https://tools.ietf.org/html/rfc4122).
Correlation-ID		Correlation-ID An unique correlation identifier correlates the request and the response messages as a pair especially useful for audit logs. Although it may be arbitrary string, it is strongly recommended to use a Universally Unique Ifentifier (UUID) version 4 form (RFC4122 https://tools.ietf.org/html/rfc4122).
Process-ID		Process-ID Identifier of a business or technical process to what the set of requests and response pairs are organized. Although it may be arbitrary string, it is strongly recommended to use a Universally Unique Ifentifier (UUID) version 4 form (RFC4122 https://tools.ietf.org/html/rfc4122).
PSU-IP-Address		PSU-IP-Address Identifier of a customer's IP address from which he/she is connected to the TPP infrastructure. It might be in the format of IPv4 o IPv6 address.
PSU-Device-OS		PSU-Device-OS A customer's device and/or operating system identification from which he/she is connected to the TPP infrastructure.
PSU-User-Agent		PSU-User-Agent A customer's web browser of other client device identification from which he/she is connected to the TPP infrastructure.
PSU-Geo-Location		PSU-Geo-Location The GPS coordinates of the current customer's location in the moment of connection to the TPP infrastructure.

Response Messages

HTTP Status Code	Reason	Response Model
201
400	The request could not be understood by the bank server due to malformed syntax. Your application should not repeat the request without modifications.
401	The request requires user authentication.
403	The bank server understood the request, but is refusing to fulfill it. Authorization will not help and the request should not be repeated.
500	The bank server encountered an unexpected condition which prevented it from fulfilling the request.
503	The bank server is currently unable to handle the request due to maintenance of the server.

Tatra banka a.s.Developer Portal

TB Accounts 1.0.1

/accounts

GET /accounts

Implementation Notes

Parameters

Response Messages

POST /accounts/information

Implementation Notes

Parameters

Response Messages

POST /accounts/transactions

Implementation Notes

Parameters

Response Messages

Tatra banka APIs

Raiffeisen bank APIs

Other Links

Contacts