Get started

Learn about starting with DECTA API and integration


When you are ready to start integration with DECTA API, just contact your DECTA Project Manager and we will provide you with further steps.


We provide two completely separate environments, one production and one test.

Both environments will have different data since the production environment will have the actual data, however, the test environment is used for testing to ensure that everything works perfectly. Nevertheless, all essential DAPI functions and requests will be available in both. In the test environment you won’t have access to real banks, but the test version provides the same features in order for you to secure that all functions work. If a new feature is added or there are any changes to existing ones, they first appear in the test environment and if everything is fine, later it is transferred in the production.

Both environments require certificates and access. A URL and a certificate for the test environment will be issued during the start of the integration, while production credentials will be issued upon completion of testing in the test environment. To streamline the integration process, all DECTA partners should fill out a questionnaire. For each client, DAPI functionality depends on their business specification and needs. Before going live, we advise clients to test their vital DAPI requests and in case of questions, contact the DECTA Support team. Also, to follow up on current updates and enhancements, we have a Changelog at dapi.decta.com



DAPI Idempotency

Idempotency ensures that repeating the same API request multiple times produces the same result as a single request. This mechanism is used to safely handle retries caused by network issues, timeouts, or client-side errors.

To use the DAPI idempotency functionality, each API request must include a Request-Id header with a unique value in UUID format in each request. Accordingly, the DECTA API response includes the same Request-Id value.

Example:

DAPI User requestDAPI response
Request with Request-Id
Example:
header: Request-Id={UUID}
payload:{"someData":"someValue"}		Response with the same Request-Id from client’s request
Example:
header: Request-Id={UUID}
payload:{"someResponseData":"someResponseValue"}

Important:

  • Request-Id for any API request must be unique in UUID format.
  • re-applying the same code Request-Id value in any of the API requests will:
    • show no error
    • produce the same result in the response as the first time
Jump to
  • DAPI Idempotency