grubhub · Rate Limits
Grubhub Rate Limits
Grubhub does not publish numeric rate-limit values for the partner / merchant APIs on its public developer portal landing pages (the portal is JavaScript-rendered and not directly fetchable). Limits are presumed to be assigned per partner integration during onboarding and enforced per OAuth client. Treat the entries below as placeholders pending direct documentation from Grubhub.
2 Limits
Throttle: 429
Rate LimitingFood DeliveryMarketplacesRestaurants
Limits
Partner integration APIs oauth-client
see partner integration documentation
Limits are assigned per OAuth client at partner onboarding; numeric values are not published publicly.
Webhook delivery (Orders, Deliveries) partner-endpoint
partner endpoint must accept burst order volumes
Grubhub posts events to the partner's webhook URL; partner is expected to absorb peak restaurant order volume rather than rate-limit.
Policies
Backoff Strategy
Use exponential backoff with jitter on 429 / 503 responses; honor Retry-After when present.
Webhook reliability
Partners receiving Orders / Deliveries webhooks should respond quickly (2xx) and process asynchronously to avoid Grubhub-side retry storms.
Per-integration scoping
Limits scoped per partner OAuth client; new integrations should pre-provision headroom with Grubhub before launch.