Many dialects.
One language.
Build against predictable Fluxcrawl objects. We translate the provider-specific fields underneath.
follower_count →stats.followers →subscriberCount →followersTikTok, Instagram, and X. One stable interface.
Less time maintaining integrations. More time building your product.
curl "https://api.fluxcrawl.dev/v1/tiktok/profile?username=example" \
-H "X-API-Key: fxc_live_xxxxx"{ "success": true, "platform": "tiktok", "data": { "username": "example", "display_name": "Example Creator", "followers": 125000, "verified": false }, "meta": { "credits_used": 1 }}Payload changes. Provider quirks. Another set of credentials. That shouldn’t be your product roadmap.
Build against predictable Fluxcrawl objects. We translate the provider-specific fields underneath.
follower_count →stats.followers →subscriberCount →followersYour code calls Fluxcrawl, not a provider. The source can change behind the same interface.
If we can’t deliver the requested data, the request doesn’t consume credits. Simple as that.
Public data from TikTok, Instagram, and X. 32 live endpoints, one key, a familiar response, and a lot to build.
Creators, conversations, and what’s next.
The people and content behind the feed.
Where the conversation happens in real time.
Live today. More platforms on the way.
Sign up and create an API key in your dashboard. One credential for every supported platform.
X-API-Key: fxc_live_••••••••Call the endpoint you need with your existing HTTP client. No new rituals.
GET /v1/tiktok/profilePut structured data to work inside your product. That was the whole point.
const { data } = response;You bring the idea. Fluxcrawl brings the public social data to build it on.
Build creator discovery, influencer tools, and marketplaces on public profiles and content.
Bring current social posts, comments, and conversations into research tools and AI applications.
Turn normalized social data into monitoring, competitive research, and marketing insights.
Start free. Add credits as your product grows. Usage-based pricing that fits the way developers build.
A little room to try your next big idea.
Get started freeOne-time purchase. Credits never expire and stack with your free credits.
Most calls cost 1 credit. X timelines, replies, searches, and follower lists, and Instagram followers, stories, highlights, and locations cost 2, since they cost more upstream. Failed calls cost nothing.
Clear answers. It’s kind of our thing.
Fluxcrawl is a developer API for public social data. It puts a stable interface between your application and upstream data sources, with predictable JSON, one API key, and usage-based credits. It covers TikTok, Instagram, and X today, across 32 endpoints.
Yes. Create an account, get 150 free credits, and generate an API key from your dashboard. Every TikTok, Instagram, and X endpoint listed on this page works against real data. The examples on this page use sample data so you can see the response shape without spending credits.
Fluxcrawl is an abstraction layer over upstream sources, which may include official APIs and third-party public-data providers. Officially, that’s “provider abstraction.” Unofficially, it means when a platform has a bad day, that’s our problem to debug, not yours. Your application integrates with Fluxcrawl rather than individual providers, and the exact source can change behind the interface without you noticing.
Common fields follow predictable Fluxcrawl objects, so “followers” means the same thing everywhere you call it. Platform-specific information stays available where it belongs. An Instagram story was never going to look like an X community, and we won’t pretend otherwise. What you shouldn’t have to do is relearn a schema every time an upstream provider quietly renames a field.
If Fluxcrawl cannot provide the requested data, the request does not consume credits. That’s a billing principle, not a promotion, and it holds everywhere Fluxcrawl charges credits. Provider errors are translated into consistent Fluxcrawl error codes, so your code branches on one contract instead of learning each platform’s excuses. When an upstream provider is down, Fluxcrawl automatically falls back to the next one where a backup exists, as it does today for TikTok and X.
Every request is fetched live from the upstream source today. Caching is planned around the type of data, since profiles, comment feeds, and stories need different cache windows, along with explicit freshness controls.
Every account starts with 150 free credits. After that, you buy credit packs rather than seats (pay for data, not for headcount), starting at $15 for 3,000 credits, and credits never expire. Most calls cost 1 credit. List endpoints that cost us more upstream, like X timelines and follower lists or Instagram followers and stories, cost 2. Every response reports its cost in meta.credits_used. You can also cap how many credits each API key can spend. Failed data requests do not consume credits, because charging you to find out a platform said no would be a strange business to be in.
Let’s make social data the easy part.
One key. Three platforms. Your next idea.