⚑Rate Limits

Understanding API usage limits


Overview

The API implements rate limiting to ensure system stability. The current limit is:

100 requests per minute (per API key)


Batch Sizes

Recommended batch sizes per entity:

Entity
Recommended
Maximum

Customers

100-500

1,000

Orders

50-200

500

Products

50-100

200

Why batch?

  • Fewer API calls = faster sync

  • Lower network overhead

  • Better error isolation


Rate Limit Headers

Every response includes:

  • X-RateLimit-Limit: Max requests per minute

  • X-RateLimit-Remaining: Requests remaining

  • X-RateLimit-Reset: Unix timestamp when limit resets


Handling 429 Responses

When you exceed the limit:

Response includes Retry-After header (seconds to wait).


Retry Strategy

Use exponential backoff when you get a 429:

Node.js Example:


Tips

1. Batch Your Requests

2. Monitor Usage

3. Stay Below Limit

Target 80-90 requests/minute to leave buffer for spikes.


FAQ

Q: What happens if I exceed the limit? A: You get a 429 response with Retry-After header. Wait and retry.

Q: Are limits per API key? A: Yes. Each API key has its own 100 req/min limit.

Q: Do failed requests count? A: Yes. All requests count toward the limit.

Q: Can I request a limit increase? A: Contact support@replen.itenvelope with your use case.


Need Help?

Contact support@replen.itenvelope for assistance.

Last updated