API Rate Limits
Trax provides APIs that customers use to:

• Connect to and work with the Trax system

• Manage master data

• Plan store visits

• Execute in the store

• Analyze visit data

​

In the past, Trax APIs did not enforce rate limits. This left our systems vulnerable to excessively high API calling rates, often caused by inefficient calling patterns or bugs in customer code that generated sudden traffic spikes.

​

 

Introducing Rate Limits

To protect system stability, we are introducing rate limits across all Trax APIs as of Oct 16, 2025:

• Every documented endpoint is now protected by a rate limiter.

• All API endpoints support a maximum of 150 requests per second.

• If a client exceeds this limit, the API will return an HTTP 429 (Too Many Requests) error.

​

 

What Customers Should Do

If your application exceeds the limit and receives a 429 error:

• Review your calling patterns to identify unnecessary or excessive requests.

• Implement exponential backoff in your API client so retries slow down automatically when 429 errors occur. This ensures your system self-corrects under load.

If your use case legitimately requires more requests per the defined time window, contact Trax Support. We will work with you and our product and engineering teams to review and, if justified, adjust your limits.