Petpooja · Rate Limits

Petpooja Rate Limits

Petpooja does not publish explicit numeric rate limits for its Online Ordering API. The API is partner-/restaurant-scoped via app key, app secret, access token, and restaurant ID, and is fronted by AWS API Gateway (ap-southeast-1), which typically enforces account- and stage-level throttling. Practical limits are governed by per-integration credentials and operational load rather than a documented public quota. Specific values are not reconciled in this artifact.

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

It captures 3 rate-limit definitions, measuring requests.

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

Tagged areas include Restaurant, POS, Online Ordering, Menu, and Food Delivery.

3 Limits Throttle: 429
RestaurantPOSOnline OrderingMenuFood DeliveryRate LimitingQuotasThrottling

Limits

API Requests integration
requests
see provider documentation
No public numeric per-minute/per-day request limit is documented for the Online Ordering API.
Menu Fetch restaurant
requests
see provider documentation
Menu/catalog fetch is scoped per restID; no documented public quota.
Save Order restaurant
requests
see provider documentation
Order push is scoped per restaurant credentials; no documented public quota.

Policies

Credential Scoping
Access is gated by app key, app secret, access token, and restaurant ID issued by Petpooja per integration.
Gateway Throttling
Requests transit AWS API Gateway, which applies platform-level throttling; specific limits are not published.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.

Sources