Zinrelo · Rate Limits

Zinrelo Rate Limits

Zinrelo does not publish specific numeric per-account or per-endpoint rate limits in its public API reference. The documentation groups endpoints into rate-limiting categories (for example a General API category referenced on the rewards endpoint), which implies category-based throttling, but exact request ceilings and windows are not published. Callers should implement pagination (start_cursor and count) on list endpoints, cache reward and tier data that changes infrequently, and apply exponential backoff on throttle responses.

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

It captures 2 rate-limit definitions, measuring requests and records.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Loyalty, Rewards, Rate Limiting, and Quotas.

2 Limits Throttle: 429
LoyaltyRewardsRate LimitingQuotas

Limits

General API Requests account
requests
not published
Endpoints are grouped into rate-limit categories (e.g. General API), but numeric ceilings are not documented.
List Pagination request
records
count default 100
List endpoints page via start_cursor and count; count defaults to 100 objects per page.

Policies

Pagination
Use start_cursor and count to page through large result sets on list endpoints such as transactions, members, and rewards.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.
Caching
Cache rewards, tiers, and other slowly-changing configuration to reduce request volume.

Sources