SocialRouter tracks provider health in real-time to ensure maximum uptime for your extractions.

​
How it works

SocialRouter monitors every extraction request and records:
  • Success/failure rate per provider, platform, and extraction type
  • Response times to detect degraded performance
  • Error patterns to identify systemic issues
This data feeds into the routing and failover logic. When a provider starts failing, SocialRouter automatically routes new requests to healthy alternatives.

​
Automatic failover

When the primary provider returns an error, SocialRouter transparently retries with the next available provider:
  1. Request sent to primary provider (cheapest or preferred)
  2. Provider returns an error
  3. SocialRouter selects a fallback provider
  4. Retry with fallback — if it succeeds, you get the result
  5. You are only charged for the successful extraction
The response always includes the provider field so you know which provider fulfilled the request. 
{
  "status": "completed",
  "provider": "brightdata",
  ...
}
Failover is transparent. Your code doesn’t need to handle retries — SocialRouter does it for you.

​
Customizing provider selection

​
Let SocialRouter decide (default)

Smart routing picks the cheapest available provider and falls back automatically. Best for most use cases.

​
Pin to a provider

If you know a provider is more reliable for your specific use case: 
{
  "url": "https://linkedin.com/in/example",
  "type": "profile.info",
  "provider": "apify"
}
Pinning disables automatic failover. If the pinned provider is down, the request will fail.

​
Per-key credit limits for safety

Use per-key credit limits to prevent runaway costs if a provider starts returning errors and triggering repeated fallbacks:
  • Set a day or hour limit on keys used in automated pipelines
  • Monitor usage via the usage endpoint

​
Best practices

1

Use automatic routing for production

Let SocialRouter handle provider selection and failover. This maximizes uptime with zero effort.
2

Monitor your extractions

Check the usage endpoint regularly to spot changes in provider distribution — a sudden shift might indicate a provider issue.
3

Set up credit limits on automated keys

Automated pipelines should have per-key credit limits to cap costs in case of unexpected provider behavior.
4

Don't pin providers unless necessary

Pinning gives you control but removes the safety net of automatic failover.