Rate Limits

To ensure fair usage and consistent performance for all developers, Nexgent applies two types of rate limits to the Public API. If you require additional API requests, please contact us at Nexgent support.

---

Quota Limits

Type	Limit	Scope	Reset Interval
Monthly quota	1,000 requests	Per user (API key)	1st of every month (UTC)

• You can make up to 1,000 successful API requests per month.
• Only responses with a status code 200–399 count toward your quota.
• Quotas reset at 00:00 UTC on the first day of each calendar month.
• If you exceed your quota, further requests will return a 429 Too Many Requests error until the quota resets.

---

Rate Limits

Type	Limit	Scope	Time Window
Per-minute rate limit	30 requests	Per user (API key)	1 minute

• You can make up to 30 requests per minute.
• If you exceed this rate limit, subsequent requests will return a 429 Too Many Requests error.
• Rate limits are enforced in rolling windows — a new minute starts counting as soon as the previous one ends.

---

Handling 429 Errors

If you hit the rate limit (429 Too Many Requests):

• Retry-After: The Retry-After HTTP header will indicate how many seconds to wait before retrying.
• Backoff Strategy: We recommend implementing an exponential backoff strategy with retries for best results.

Example 429 response:

{
  "error": {
    "message": "Too many requests. Please wait and try again.",
    "type": "rate_limit_error"
  }
}

---

Best Practices

• Implement automatic retry logic with exponential backoff.
• Batch your requests whenever possible to minimize unnecessary API calls.
• Cache responses locally when appropriate to avoid redundant requests.

---

Summary

Limit Type	Limit	Scope	Reset
Monthly Quota	1,000 requests	Per user (API key)	Monthly (1st, 00:00 UTC)
Per-Minute Rate	30 requests/minute	Per user (API key)	Every rolling minute

---

More Information

For additional help with rate limits or to request higher limits for your application, contact Nexgent support.