Rate Limits and Pagination

API endpoints are protected with request throttling. Collection endpoints use offset pagination for deterministic traversal in reporting and reconciliation jobs.

Rate Limit Headers

  • X-RateLimit-Limit total requests allowed in the window.
  • X-RateLimit-Remaining requests left in the window.
  • Retry-After wait time in seconds when throttled.
429 response example
{
  "success": false,
  "error": {
    "code": "RATE_LIMIT_EXCEEDED",
    "message": "Too many requests. Retry after 10 seconds."
  }
}
GET https://api.tinkerpayments.com/v1/reconciliation/lines?limit=50&offset=0
{
  "success": true,
  "data": {
    "items": [{ "id": "line_1" }],
    "limit": 50,
    "offset": 0,
    "total": 321
  }
}

For background jobs, use incremental backoff with jitter on 429/5xx responses and persist cursor state (limit/offset) between runs.