Gingr · Rate Limits

Gingr Rate Limits

Gingr does not publish fixed numeric rate limits for the Partner API (api.gingr.io) in its public OpenAPI/Swagger document, Postman collection, or support articles. Access is scoped per facility via an X-Api-Key header plus a subdomain header identifying the account; there is no documented requests-per-minute ceiling, burst limit, or published 429 policy. Most list endpoints are cursor/offset paginated with a page[size] enum capped at 100 items per page, which caps the practical cost of any single request rather than the request rate itself.

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

It captures 3 rate-limit definitions, measuring requests, items, and keys.

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

Tagged areas include Pet Care, Pet Daycare, Rate Limiting, and Quotas.

3 Limits Throttle: 429
Pet CarePet DaycareRate LimitingQuotas

Limits

Partner API Requests account
requests
not published
No fixed numeric request-rate limit is documented for api.gingr.io.
List Endpoint Page Size request
items
100
page[size] is an enumerated value (10, 25, 50, or 100) on most list endpoints; 100 is the largest documented page.
API Key Scope account
keys
per facility subdomain
Each X-Api-Key is issued per Gingr account/subdomain from the Manage Account API area; it is not a shared or platform-wide key.

Policies

Read-Only Legacy Endpoints
Gingr's older subdomain-scoped reporting endpoints (referenced in legacy support articles) are documented as read-only; the current Partner API adds full CRUD on owners, pets, and bookings.
No Published Backoff Guidance
Gingr's public docs do not specify a Retry-After header or backoff recommendation; integrators should apply conservative exponential backoff on 429/5xx responses as a precaution.

Sources