[#1466] API usage tracker

Migrated from Redmine #1466 | Author: JM Kuizon
Status: Feedback | Priority: High, I’m very impatient | Created: 2025-08-29


Hi,

How can we track our API usage tracker

Putting the priority, to high, as we are already live

Dmytro Bondarev wrote:

Hi, at the moment you can count API calls on your end and rely on related (status 429)

JM Kuizon wrote:

Dmytro Bondarev wrote in #note-1:

Hi, at the moment you can count API calls on your end and rely on related (status 429)

What does status 429 means?

Is there any update on this one?

HTTP status 429 means “Too Many Requests”. The server is rate limiting you: you sent more requests in a given time window than it allows.

Status 429 only tells you that a limit was hit; it does not give a usage total. For tracking, log each API request on your side with timestamp, endpoint and API key, then aggregate per day or month against your plan limit. Treat 429 as a throttling signal and back off; if the API returns rate-limit headers such as Retry-After, use them, but don’t assume they are always present.

Hi,

Thank you for your patience, and sorry for the delay.

At the moment there is no built-in API usage counter or dashboard that shows how many requests your account has made. The way to track your usage is on your side:

  • Log each API request in your integration with the date and time, the endpoint and the response status, and count the requests per day.
  • Treat a 429 response (Too Many Requests) as a signal that you have hit a limit: wait, then back off progressively and retry. If the response contains a Retry-After header, use it, but please don’t rely on it always being present.

The API limits that apply to your account are described in our Terms and Conditions, section 4.2 (and section 2.4 for
enterprise plans), so you can compare your own request counts with them

We have noted your request for an API usage tracker. We will consider iit will be implemented or give any timeline.

Best regards,
Vitalii