1
Create a scraper key
Open the Scraper dashboard, choose API Keys,
and click Create key.Copy the key immediately. The full value is shown only once; the dashboard keeps only
a truncated preview. Scraper keys begin with
scrape_live_.2
Store the key on your server
Keep the key in a secret manager or server-side environment variable. Do not put it
in browser code, a mobile app, or a repository.
Scraper keys are separate from SideShift Platform and Connect credentials. Other
SideShift key types are rejected on scraper routes.
3
Request a profile
Send a
POST request with JSON and the x-api-key header.4
Read the envelope
The resource payload is in Log
data. Request tracing and billing metadata are always
outside it.request_id, meta.credits_charged, and meta.credits_remaining for every
request. Standard profile, post, posts-page, and platform-operation lookups cost one
credit; TikTok audience costs 25. If your account has negotiated rates, the dashboard
and meta.credits_charged show the exact amount.Fetch a page of posts
Change the resource toposts. The normalized listing response contains posts,
profile_pictures, and next_cursor when another page is available.
next_cursor back as cursor. Never parse, edit, or construct a cursor.
posts rate (one credit at
the standard rate). Snapchat and LinkedIn listings are single-page only and never return a
cursor.
Production checklist
- Use a background job for scraping rather than blocking an interactive page request.
- Set a request timeout of at least 60 seconds; use 90 seconds for YouTube and Facebook.
- Store platform post
idplusplatformas your deduplication key. - Download short-lived media URLs instead of saving the URL.
- Retry only transient, refunded failures and honor
Retry-Afteron429responses.
Understand responses
Learn the normalized and platform-specific data contracts.
Add safe retries
Copy the retry wrapper and review billing rules before going live.