1. Integration
Partner API
  • Getting Started
    • Introduction
    • Authentication
    • Business Use Cases
  • API References
    • Balances & History
      • Get Balances
      • Get Balance History
    • Crypto Deposits
      • Get Crypto Deposit Details
      • Add Travel Rule
    • Crypto Withdrawals
      • Get Whitelisted Wallets
      • Add Whitelisted Wallet
      • Delete Whitelisted Wallet
      • Create Crypto Withdrawal
      • Get Crypto Withdrawal Details
    • SEPA Deposits
      • Get SEPA Payment Details
      • Get SEPA Deposit Details
    • SEPA Withdrawals
      • Create SEPA Withdrawal
      • Get SEPA Withdrawal Details
    • Currency Exchange
      • Get Rates
      • Create Lock
      • Create Exchange
      • Get Exchange Details
  • Integration
    • Integration Guides
    • Transaction Processing
    • Error Handling
    • Rate Limiting
    • Webhooks
      • Crypto Deposit Webhook
      • Crypto Withdrawal Webhook
      • SEPA Deposit Webhook
      • SEPA Withdrawal Webhook
      • Exchange Webhook
  • Reference
    • Supported Currencies
    • Fees
    • FAQ
    • Changelog
    • Support
  1. Integration

Rate Limiting

This page explains how rate limiting works in the Fintegence Partner API and how to build a client that behaves safely under traffic constraints.
Rate limits
The Partner API limits the number of requests per IP address to keep the service fast and reliable for all partners. The limits are sufficient for typical integrations. If you expect a consistently high request volume, contact support@fintegence.com.

Why Rate Limiting Matters#

Rate limiting is not only a restriction mechanism. It is a core reliability and protection feature.
Security: Helps protect the API against abusive traffic patterns, brute-force attempts, and denial-of-service behavior.
Performance: Preserves stable response times across all integrations, even under elevated traffic.
Fair Usage: Prevents a single client from monopolizing shared API resources.
Stability: Reduces the risk of service degradation caused by bursts, bots, or inefficient polling loops.

Handling Exceeded Limits (429 Too Many Requests)#

When the limit is exceeded, the server rejects the request with HTTP 429 Too Many Requests. A request rejected with 429 is not processed, so it is safe to retry it after waiting.
If the response includes a Retry-After header, wait at least the number of seconds it specifies before retrying. Otherwise, retry with exponential backoff - for example after 1, 2, 4 and 8 seconds.

Best Practices for Integration#

A reliable client should anticipate rate limiting and react gracefully.

1. Avoid Aggressive Polling#

Polling loops for asynchronous operations should be rate-aware. If you are tracking deposits, withdrawals or exchanges, prefer webhooks over tight polling intervals.

2. Batch Thoughtfully#

Where possible, avoid unnecessary request bursts. Reuse previously fetched data, debounce user-triggered refresh actions, and avoid parallel request storms from the same IP.

3. Retry Carefully#

Retry only requests rejected with 429 or 5xx, with increasing delays between attempts. Do not retry 4xx validation errors without changing the request. For withdrawals and exchanges, check whether the transaction was created before retrying a request that timed out (see Transaction Processing).
Enterprise Traffic
If your integration is expected to generate consistently high request volume, contact support@fintegence.com to discuss whether your traffic profile requires a different operational setup.
Previous
Error Handling
Next
Webhooks
Built with