Reliability for live social fetches
Live upstream lookups across 21 platforms (165 operations). requestId, typed outcomes, measured uptime — not a contractual SLA.
Live fetch, not a shared cache
Every lookup hits the platform at request time — no shared cache serving stale profiles. Average latency ~~3.2s on live fetches.
When a platform changes markup, we fix the adapter. Your code keeps the same field names.
What we mean by reliability
99.8% uptime is a rolling 90-day public API measurement — not a contractual SLA or guarantee against upstream outages.
Completed not_found or private is a successful HTTP response and may bill per operation docs. Infrastructure failures do not charge.
Terms do not invent availability commitments. Custom SLAs require a separate agreement.
Current measured status
Rolling public numbers we publish on the marketing site. For a liveness probe, call GET /health on the API (docs linked below).
99.8%
Uptime
Measured across the public API over the last 90 days
~3.2s
90-day avg response
Rolling mean latency on live upstream fetches — no cache in front
165
API endpoints
Marketplace operations on one key
21
Platforms
OpenAPI marketplace tags
What you get when something breaks
requestId on every response
Paste meta.requestId into support and we can trace the upstream attempt. No guessing which call failed at 2am.
lookupStatus before you parse
found, not_found, private, and related outcomes sit in data — not as an empty array you have to interpret.
No charge when we break
Infrastructure failures do not touch your balance. You pay for completed lookup attempts, not our scraper having a bad hour.
Health for monitors
GET /health is unauthenticated liveness. Point uptime checks there; do not page yourself on a single not_found profile.
Docs and status checks
- Health check
GET /health — liveness probe, no auth, no credits.
- Errors and outcomes
Success vs error envelopes, lookupStatus, and when to retry.
FAQ
Do you publish a contractual uptime SLA?
No. The 99.8% figure is a rolling 90-day measurement on the public API, not a contractual guarantee. Platform outages and upstream blocks sit outside any percentage we publish. Custom availability terms require a separate agreement.
Where do I check if the API is up?
Call GET /health on api.socialfetch.dev (documented under Health check). For support on a bad response, send meta.requestId to support@socialfetch.dev.
Why is average latency around 3 seconds?
Live fetches against social platforms take longer than reading a shared cache. The published ~3.2s figure is a rolling mean on those live lookups — not a CDN hit.
Are not_found responses failures?
HTTP 200 with lookupStatus not_found (or private) means the lookup completed and the domain outcome is explicit. That is different from a 5xx or infrastructure error. Billing follows the operation docs — completed attempts may still charge.
What happens when a platform changes its HTML?
We update the adapter. Your client keeps the same OpenAPI field names. You should not need to rewrite parsers for every DOM shift.
Does reliability cover all 21 platforms?
The uptime measurement is for the public API service. Individual platforms can still return not_found, private, or temporary upstream errors. Coverage is the same catalog as the rest of the product — 21 marketplace platforms and 165 operations.
Start with 100 free credits
No card. Call a live profile route, keep the requestId, and see the envelope yourself.