Thanx · Rate Limits

Thanx Rate Limits

Thanx does not publish numeric request-rate or concurrency limits in its developer documentation, and the documented error catalog does not include a 429 / Too Many Requests code. The actionable throughput guidance Thanx does publish is batch-oriented: reward issuance via the Partner API should collect identifiers and submit them in batches of up to 10,000 per request for optimal throughput and to avoid rate limiting. Collection endpoints are paginated. Treat the numeric values here as documentation-derived guidance rather than contractual limits; confirm production limits with Thanx.

Thanx Rate Limits is the machine-readable rate-limit profile for Thanx on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring requests_per_second, identifiers_per_request, and seconds.

The profile also includes 3 backoff/retry policies defined and response codes documented for badRequest, unauthorized, forbidden, and notFound.

Tagged areas include Rate Limiting, Loyalty, Guest Engagement, and Restaurant.

3 Limits
Rate LimitingLoyaltyGuest EngagementRestaurant

Limits

General request rate client
requests_per_second
not published — confirm with Thanx
No per-second or per-minute request limit is documented. No 429 response code is listed in the Consumer API error catalog.
Reward issuance batch size (Partner API) account
identifiers_per_request
10000
Submit campaign reward identifiers in batches of up to 10,000 per request to the Issue Rewards endpoint for optimal throughput and to avoid rate limiting. Issuance is processed asynchronously via an issuance job.
Partner access token lifetime token
seconds
3600
Privileged end-user access tokens accept an optional expires_in between 60 and 3600 seconds.

Policies

Batch over loop
Prefer batched reward issuance (up to 10,000 identifiers per request) over issuing rewards one at a time; this is the documented mechanism for avoiding rate limiting.
Asynchronous processing
Reward issuance returns 202 Accepted with an issuance job; poll the issuance-job endpoint for completion rather than blocking.
Pagination
Collection endpoints (rewards, purchases, locations, campaigns, users) return a pagination object (total_page, per_page, current_page); page through results instead of requesting large pages.

Sources