API rate limits
Understand default limits and how to avoid throttling.
Prerequisites
- Valid Pam Pod-scoped API key
Rate limits protect shared infrastructure. Excessive request rates receive 429 responses with retry guidance. Batch reads where possible and honor Retry-After headers.
Expected result
Integrations stay below rate limits with stable retry behavior on transient 429 responses.
If something goes wrong
If you hit sustained throttling, reduce poll frequency or contact cs@pamphlet.io with your integration pattern for enterprise limits.
