PetExec · Rate Limits

Petexec Rate Limits

PetExec does not publish any numeric request-rate limits, throttling behavior, or 429 policy for its API in the public GitHub examples repository or on petexec.net. The only access-control mechanism documented is OAuth2 scoping (e.g. owner_read, owner_update, usercard_read, menu_read, report_read) requested per access token via the password grant against POST /token - narrower scopes limit what a token can call, but nothing in the public material describes a request-per-minute or request-per-day cap.

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

It captures 3 rate-limit definitions, measuring requests, scope, and seconds.

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

Tagged areas include Pet Care, Boarding, Daycare, Grooming, and Rate Limiting.

3 Limits Throttle: not documented
Pet CareBoardingDaycareGroomingRate Limiting

Limits

API Requests account
requests
not published
No numeric rate limit is documented anywhere in PetExec's public API materials.
OAuth2 Scopes token
scope
per requested scope
Access is bounded by the space-separated scopes requested at token time (e.g. owner_read, owner_update, usercard_read, menu_read, report_read), not by a call-volume limit.
Access Token Lifetime token
seconds
not published
The password-grant token response includes an expires_in field in the examples, but PetExec does not publish a standard token lifetime.

Policies

Client Credential Handling
Client secrets are self-issued in-app (Company Preferences > Misc. Settings > Maintain API Applications) and should not be embedded in public/browser-side clients; PetExec's own JavaScript examples flag this explicitly but still ship the client_secret variable in client-side code as a placeholder.
Backoff Strategy
Not specified by PetExec. As a general practice, clients should implement exponential backoff with jitter on 401/5xx responses since no documented 429 behavior exists to key off of.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/petexec-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.