Skip to main content
Publicly available data from the platforms we support — profiles, posts, media, comments, and pages. See the full list on the Platforms page. Scraperize returns only what is publicly visible; it never accesses private or logged-in-only content.
With prepaid credits. Each successful request costs 1 credit; a cache hit costs 0, and errors are never charged. Credits are bought in one-time packs; you spend from your balance as you scrape, and unused credits never expire. See Credits.
No. Credits are a balance you spend as you scrape (about 1 per request) — whatever you don’t use stays on your account, with no monthly reset.
Requests return 402 INSUFFICIENT_CREDITS. Buy another pack from your dashboard and you’re topped up immediately — existing credits are unaffected.
Add cache_max_age to your requests to accept a recent cached result for 0 credits. Pick the largest freshness window your use case allows. See Caching.
Requests are limited per team per minute. Over the limit returns 429 with a Retry-After header; back off and retry after that many seconds. See Rate limits.
Switch on the stable error.code, show error.message to users, and log error.requestId (include it in support requests). See Errors.
19 platforms and 87 endpoints today — see Platforms — and we add more over time. Need one that isn’t listed? Tell us; the roadmap follows demand.
Your API keys and usage are private to your team. Keep your API key secret and call the API from your server, never from client-side code. See Authentication.
Scraperize returns public data, but you are responsible for using it in line with the applicable platforms’ terms and the laws that apply to you. Use it to build responsibly.
Still stuck? Reach out from scraperize.com with your requestId and we’ll help, or find us on X (@scraperize).