API rate limits

Learn about API rate limits and how to work with them.

Rate limits

At Fintoc, we have implemented rate limits to ensure the stability and performance of our API and widget connections. These rate limits help prevent excessive traffic and ensure fair usage of our services. We have two types of rate limits in place:

  1. IP Rate Limit:

    • Requests per IP: 100 requests per 10 seconds.
    • This limit applies to each unique IP address accessing our API.
    • It helps prevent abuse and ensures a smooth experience for all users.
  2. Widget Connection Rate Limit:

    • Requests per Organization: 100 requests in a window duration of 130 seconds.
    • This limit applies to the widget connections made by each organization.
    • It allows organizations to maintain a reasonable level of activity without overwhelming the system.

Please note that these limits are set as maximums, and we encourage users to avoid generating unnecessary load on our servers. If you encounter rate-limited responses, make sure to handle them gracefully.

We continuously monitor and adjust our rate limits to prevent abuse and accommodate high-traffic scenarios. Our goal is to provide a reliable and efficient service to all our users.

We may reduce limits to prevent abuse, or increase limits to enable high-traffic applications. To request an increased rate limit, please contact support. If you’re requesting a large increase, contact us 1 month in advance of when you’ll need the increased rate limit.

If you have any questions or concerns regarding our rate limits, please don't hesitate to reach out to our support team for assistance.

Handling Limiting Gracefully

To ensure a smooth integration and graceful handling of rate limiting, we recommend implementing the following technique:

  • Monitoring for 429 Status Codes and Retry Mechanism:
    Watch for 429 status codes in API responses and implement a retry mechanism when necessary.
    Use an exponential backoff schedule for retries to reduce request volume.
    Consider adding randomness to the backoff schedule to prevent a thundering herd effect.

By following these best practices, you can optimize your integration with Fintoc API and ensure a smooth experience while working within the defined rate limits.