Each generated endpoint page repeats its applicable bucket under Requirements. An endpoint without a displayed named bucket is still subject to its documented domain rules, sending quota, and protective platform controls.
Rate-limit response
When a named HTTP bucket is exhausted, Apollo Signal returns429 as an application/problem+json document and includes:
Retry-After is a whole number of seconds. Wait at least that long, then retry with jitter so concurrent workers do not all resume at once.
X-RateLimit-Remaining or reset headers are present.
Sending quotas
Email delivery also has plan-backed quotas independent of the HTTP request bucket:- A project has a per-second send allowance.
- An organization has a daily send allowance.
- A batch or audience fan-out consumes quota per resulting message, not merely per HTTP request.
- Scheduled and test-mode behavior follows the send endpoint’s response and plan rules.
429. Inspect the problem code, honor Retry-After, and do not bypass the quota by rotating API keys.