Premium API - Accounts

Download OpenAPI 2.0 specification (swagger for v2 version)

Currently supported versions

Title:
Premium API - Accounts
Version:
2.0
Protocols:
HTTPS

 

Title:
Premium API - Accounts
Version:
1.1
Protocols:
HTTPS

API Description

Premium API - Accounts allows easy interaction with your accounts in Tatra banka, allowing the following operations:

  • List of accounts
  • Account detail and balances
  • Account transactions

Additionally, if you are using Premium API - Accounts as a TPP, you can use endpoints connected to the consents:

  • creation of the consent
  • checking the status of the specific consent
  • deletion of the specific consent

Premium API - Accounts is available also in testing (Sandbox) environment to test your applications before accessing the production data.

Specific settings for Premium API - accounts

If you are planning to use Premium API service, you should create an application with following settings:

Scope: PREMIUM_AIS

Callback URL for Sandbox environment: https://developer.tatrabanka.sk/resources/oauthCallback.html

Application Usage: Final consumer or TPP (Third Party Provider)

 

Different usage types of Premium API - Accounts 

Premium API offers two different types of Application Usage to its consumers. If you are a Premium API - Accounts consumer, you are able to use them in two different scenarios:

  • Final consumer: this application usage enables you to access your accounts held in Tatra banka
  • TPP: this application usage enables you to access user´s accounts held in Tatra banka, after consent has been granted by the user. In order to distinguish between different users, you have to use consent API endpoints. ConsentId is inserted after scope and colon (e.g. PREMIUM_AIS:2d5d8c-1d5fd8d-2x36d5-2d1g5g)

Usage of Consent endpoints in TPP Usage type

If you are using Premium API - Accounts service as TPP, you have to use consent endpoints in your implementation. Users are distinguished mainly by consentIds (unique IDs) which are used specifically in authorize calls (you have to insert consentId after scope and colon of the authorize call).

You are able to:

  • create consent with POST /v1/consents call
  • check the status of consent with GET /v1/consents/{consentId} call
  • delete the consent with DEL /v1/consents/{consentId} call

Technical break

Account information are available non-stop, except during the daily closure (technical break) lasting approx. 30 minutes, 1.5 hours on Saturdays, which is usually on business days from 9:45 p.m. to 10:45 p.m. and on Saturdays from 9:45 p.m. to 11:45 p.m. During technical break system is off-line.