The DEUNA API is a set of REST APIs that allow you to use DEUNA services from your server to integrate in a personalized way.
Browse the set of categorized APIs in our documentation:
Authentication
The DEUNA APIs are authenticated by X-API-Key provided by your DEUNA TPM.
Environments
DEUNA APIs work in two environments:
Sandbox https://api.sandbox.deuna.io
Production <https://api.deuna.io>
- Sandbox: In this environment you can use test credentials to integrate our services and perform all necessary tests.
- Production: In this environment, you must have your production credentials, with which you can start generating transactions.
Payment processing time
The processing time for each payment /purchase request varies depending on the third-party executing the transaction.
The total processing time is the sum of:
- The processing time of DEUNA.
- The processing time of the processor or acquirer.
- The processing time of the anti-fraud provider.
Timeout
DEUNA uses a timeout value of 60 seconds for all APIs. Therefore, the total time available for a request to be processed and answered by our APIs is 60 seconds.
The 60-second timeout covers all third-party vendor cases, as their response time varies.
It is recommended to maintain a timeout value longer than 60 seconds to comply with the transmission process.
API updates
DEUNA continuously updates the APIs to ensure compatibility and quality:
Versioning and disruptive changes
When a significant change is made to the DEUNA API, DEUNA releases a new version.
This allows you to upgrade at a time that is convenient for your business without disrupting your existing integration.
Backwards-compatible changes
DEUNA classifies the following modifications as backwards compatible:
- Add new resources to the API.
- Introduce new optional request parameters to existing API methods.
- Include new properties in existing API responses.
- Change the order of properties in existing API responses.
- Adjust the length or format of opaque strings (for example, object identifiers, error messages, and other human-readable strings), including adding or removing prefixes.
- Introduce new event types. Make sure your webhook receiving service can handle unknown event types.
Rate limits
DEUNA API implements usage limits to ensure service quality for concurrent users in the platform.
Limits are applied at the account level, regardless of the authentication credentials used.
You might need to make rate limits adjustments to to prevent system misuse.
Concurrent rate limits
Concurrent rate limits set the maximum number of simultaneous requests-per-second (RPS) allowed on DEUNA API. The standard limits are outlined below:
- Read operations limit: 100 RPS live mode and 25 RPS in sandbox mode.
- Write operations limit: 100 RPS live mode and 25 RPS in sandbox mode
These rate limits are aggregated across all APIs.
Exceeding a rate limit triggers a HTTP 429 response, and the request can be safely retried. To avoid frequent rate limit hits, use a retry strategy with incremental changes and setbacks.
Data products and reporting products are excluded from rate-limiting rules.
Load testing
You might need to load test your systems for increased throughput scenarios such as major sales events.
While the sandbox environments are designed for testing functional integration aspects, load testing is discouraged due to lower rate limits in testing environments.
Instead, you can simulate requests to DEUNA with a reasonable latency level applied.
If you have complex integrations that require specific load testing windows or an increment of the rate limits, contact your DEUNA TPM or Account Manager.