provider slug, and we normalize the response. If multiple actors back the same slug, we transparently retry on failure — opt out per request with fallback: false. Two endpoints share the same slug grammar: POST /v1/extract for URL-driven jobs and POST /v1/search for query-driven ones (e.g. Google Maps place search).
Why SocialRouter
One API, any provider
Switch providers by changing one parameter — the
provider slug. No migration, no rewrite.Automatic failover
When a provider returns an error or rate-limits you, SocialRouter retries on the next compatible provider in the same call.
Pay per extraction
No subscriptions. Compare providers side-by-side and pin the cheapest or fastest.
How it works
1
Get your API key
Sign up and create an API key from the dashboard.
2
Send an extraction request
POST a social URL and a
provider slug (e.g. apify/linkedin/profile.info) to /v1/extract. SocialRouter handles routing and normalization.3
Get normalized data
Receive a clean, consistent response regardless of which provider fulfilled the request.
Supported platforms
Coverage is derived from the live provider registry — new combinations appear automatically as providers are added. Query
GET /v1/providers for the authoritative catalogue. The browsable list with copy-ready slugs lives at socialrouter.io/providers.Next steps
Quickstart
Make your first extraction in under 2 minutes.
API reference
Full endpoint documentation with interactive playground.