Skip to main content
Triqai applies rate limits to ensure fair usage and maintain service reliability. Rate limits vary by plan and are applied per organization.

​
Rate Limits by Plan

PlanRequests per Minute (RPM)Requests per Second
Free60 RPM1 RPS
Starter300 RPM5 RPS
Growth600 RPM10 RPS
Business1,200 RPM20 RPS
EnterpriseCustomCustom
Rate limits are calculated using a sliding window algorithm with per-second granularity for precise control.

​
Rate Limit Headers

Every API response includes rate limit information in the headers:
HeaderDescription
X-RateLimit-LimitMaximum requests allowed per window
X-RateLimit-RemainingRequests remaining in current window
X-RateLimit-ResetISO timestamp when the limit resets
Example response headers: 
X-RateLimit-Limit: 10
X-RateLimit-Remaining: 7
X-RateLimit-Reset: 2026-01-19T10:30:01.000Z

​
Rate Limit Exceeded

When you exceed the rate limit, you’ll receive a 429 Too Many Requests response: 
{
  "success": false,
  "error": {
    "code": "rate_limited",
    "message": "Rate limit exceeded. Maximum 10 requests per second. Retry after 234 milliseconds."
  },
  "meta": {
    "generatedAt": "2026-01-19T10:30:00Z",
    "requestId": "3c90c3cc-0d44-4b50-8888-8dd25736052a123",
    "version": "0.1.0"
  }
}
Additional headers on 429 responses:
HeaderDescription
Retry-AfterMilliseconds to wait before retrying

​
Best Practices

Instead of enriching transactions one at a time in rapid succession, batch them and process at a controlled rate.
For large batches, consider processing asynchronously rather than blocking on immediate results.
Track rate limit metrics in your dashboard to understand usage patterns and plan capacity.
If you’re consistently hitting rate limits, consider upgrading your plan for higher limits.

​
Upgrading Rate Limits

If you need higher rate limits:
  1. Upgrade your plan: Higher tiers include increased limits
  2. Contact sales: For enterprise needs, we offer custom rate limits

View Pricing

Compare plans and rate limits

​
Rate Limits Per Endpoint

All authenticated endpoints share the same rate limit pool. The limits apply to:
  • POST /v1/transactions/enrich
  • GET /v1/transactions
  • GET /v1/transactions/{id}
  • DELETE /v1/transactions/{id}
  • GET /v1/categories
  • GET /v1/merchants/{id}
  • GET /v1/locations/{id}
  • POST /v1/report-issue
Read-only endpoints (GET requests) count toward the same limit as enrichment requests. Design your application to minimize unnecessary API calls.

​
Next Steps

Credits

Learn about credit consumption and billing

Error Handling

Handle rate limits and other errors gracefully