API limits and best practices
The Agency plan includes 5,000 API calls per day; here is how to stay within that limit and build reliable, secure integrations.
Last updated Oct 27, 2026
The PixelSpyer API is available on the Agency plan with an allowance of 5,000 calls per day. This article explains how the limit works and how to build integrations that stay reliable and secure.
The daily limit
| Plan | API access | Calls per day |
|---|---|---|
| Free | No | None |
| Starter | No | None |
| Pro | No | None |
| Agency | Yes | 5,000 |
Daily limits reset at midnight UTC. See /api-docs for endpoints, authentication and examples.
Stay within your allowance
- Cache results. The ad library is a periodically refreshed snapshot, not a real-time feed, so requesting the same data many times a day adds little. Store responses and reuse them.
- Request only what you need. Where an endpoint supports filters or parameters, use them to narrow requests instead of fetching broadly and filtering on your side.
- Spread out large jobs. Run big jobs at a steady pace through the day rather than all at once.
- Count your calls. Track usage in your own code so you know how close you are to 5,000.
- Plan around the reset. If you are close to the limit, schedule the rest of the work for after midnight UTC.
Build reliable integrations
- Handle errors gracefully. If a request fails, wait before retrying and lengthen the wait with each attempt, rather than retrying in a tight loop.
- Expect missing fields. Not every ad has every detail. Some older ads have no preview, and EU reach estimates are only present when available.
- Log your requests. Simple logs make problems much quicker to find.
- Test small first. Try a few requests before running a large job.
Keep keys secure
- Keep API keys on your server. Never embed them in front-end code, where anyone can read them.
- Do not share keys or paste them anywhere public.
- Revoke and replace a key straight away if you think it has been exposed. See Creating and managing API keys.
Use the data responsibly
The ads come from the public Meta Ad Library and belong to the brands that ran them. Use API data for research and analysis, not to republish other brands' creative as your own. PixelSpyer is not affiliated with Meta.
Questions about your use case
If you are unsure whether the API fits what you want to build, contact us through /contact or at [email protected].
Related
Was this article helpful?
Still need help? Contact support or email [email protected].