Skip to main content
Every API key has a per-second rate limit and a daily request limit, both set by Noyax. Both counters are kept per API key: all of your servers using the same key share the same limits. The per-second limit is checked first on every request; if it rejects a request, that request is not counted against the daily limit.

Headers

Every response that passes the permission check includes your remaining allowance for both limits:

When a limit is reached

Once a limit is used up, requests are not processed and the API returns 429:
The per-second counter resets at the start of the next second; retrying immediately after will succeed once you are back under the limit. The daily counter resets every day at midnight Turkey time (UTC+3); retrying on the same day after a daily 429 will not succeed.

What counts?

  • All requests that pass token, header and permission checks count, including those that end with a business rule error (400, 404).
  • Requests rejected with an invalid token (401), a header error (400) or a permission error (403) do not count.
  • A request rejected for exceeding the per-second limit does not count against the daily limit either.

Tips

  • Use a large pageSize (up to 50) on list endpoints to reduce the number of requests.
  • Cache data that rarely changes on your side.
  • Spread bulk operations out instead of firing them all at once, to stay under the per-second limit.
  • Watch X-Daily-Remaining and postpone bulk jobs when it runs low.
  • If you need a higher limit, contact Noyax support. The new limits take effect when you get a new token.