Introduction
One stable API for live public and social data.
Fluxcrawl gives you one API for live public data instead of a separate,
fragile integration for every platform you touch. Call
/v1/{platform}/{endpoint}, get back the same shape every time, regardless of
which upstream provider actually answered the request underneath.
The web keeps changing. Fluxcrawl's job is to make sure your interface to it doesn't.
Get started in two minutes
TikTok, Instagram, and X are live, 32 endpoints against real data.
Sign up for 150 free credits, create a key
in the dashboard, and send it in the
X-API-Key header. See Authentication.
How it works
Every platform/endpoint pair is served by one or more provider adapters, tried in order. If the first one is down, Fluxcrawl falls back to the next one automatically. You never see which provider actually answered, and you never have to handle that failover yourself.
route → fetch (fallback on provider failure) → normalize → respondTikTok, X, and Instagram's most-used endpoints each have more than one upstream provider behind them today. You always get the same normalized schema back regardless of which one actually served a given request. Which provider answered is an implementation detail Fluxcrawl handles for you, not something you need to know or configure around.
Response shape
Every successful response looks like this:
{
"success": true,
"platform": "tiktok",
"data": { ... },
"meta": { "credits_used": 1 }
}data is always shaped the same way for a given endpoint, whichever provider
served it. Each endpoint's API reference page shows
its exact data shape with a real example.
Failures look like this instead:
{
"success": false,
"error": { "code": "RESOURCE_NOT_FOUND", "message": "..." }
}See Errors for the full list of codes and what each one means.
Quick example
curl 'https://api.fluxcrawl.dev/v1/tiktok/profile?username=tiktok' \ -H 'X-API-Key: YOUR_KEY'{
"success": true,
"platform": "tiktok",
"data": {
"username": "tiktok",
"display_name": "TikTok",
"followers": 95800000,
"verified": true
},
"meta": { "credits_used": 1 }
}That response is real, live data from the actual endpoint, not a mock.