Rate Limits
Understand the current NextSign API request limit and how to build retry-safe clients around it.
Rate Limits
The current documented rate limit for the NextSign API is 100 requests per minute.
Design your integration so it stays below the limit during normal traffic and during retries after transient failures.
Practical Guidance
- Queue outbound requests from your backend instead of firing large bursts at once
- Limit concurrency for write operations such as case creation and form submission
- Cache repeated reads where it makes sense
- Avoid automatic retry storms after timeouts or network errors
How to Handle Throttling
If your client is throttled or you receive temporary failures:
- Stop sending immediate repeat requests
- Retry with exponential backoff and jitter
- Keep write operations idempotent on your side
- Resume gradually instead of sending a full burst again
Suggested retry pattern for your own client:
- Retry 1: after 1 second
- Retry 2: after 2 seconds
- Retry 3: after 4 seconds
- Retry 4: after 8 seconds
- Retry 5: after 16 seconds
If your HTTP client receives a Retry-After header, follow that value before applying your own schedule.
Planning for Production
Treat 100 requests per minute as a hard planning ceiling for your integration. If your use case includes imports, bulk signing flows, or scheduled jobs, add buffering and queueing in your application layer.
Test Environment
Validate your throughput strategy in the test environment before going live:
- confirm your retry behavior
- confirm your queue drains at an acceptable pace
- confirm your UI or backend degrades gracefully when requests are delayed