requestId on every response
Paste meta.requestId into support and we can trace the request. No guessing which call failed at 2am.
Reliability
Reliability for live social fetches
Live lookups across 25 platforms (264 operations). requestId, typed outcomes, measured uptime — not a contractual SLA.
Model
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.
01
Request
Your call hits the API — no shared cache in front.
02
Fetch
Every lookup hits the platform live, at request time.
03
Adapt
Markup shifts absorbed in the adapter — your fields stay stable.
04
Respond
A typed outcome:
lookupStatusplusrequestIdon every call.
Meaning
What we mean by reliability
99.8% uptime is rolling 90-day API availability — whether Social Fetch answered. It is not a contractual SLA or a guarantee against platform outages.
98.4% request success is the share of production lookups that completed without an infrastructure failure. Completed not_found or private is a finished lookup, not downtime, and may bill per operation docs. Infrastructure failures do not charge.
Terms do not invent availability commitments. We publish uptime openly instead of selling an SLA.
Numbers
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
98.4%
Request success
Production lookups that completed without an infrastructure failure
~3.2s
90-day avg response
Rolling mean latency on live fetches — no cache in front
25
Platforms
OpenAPI marketplace tags
Guarantees
What you get when something breaks
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
Docs and status checks
FAQ
Reliability FAQ
Do you publish a contractual uptime SLA?
No. The 99.8% uptime figure is a rolling 90-day measurement on the public API, not a contractual guarantee. Platform outages and platform blocks sit outside any percentage we publish. We publish uptime openly instead.
What is the difference between 99.8% uptime and 98.4% request success?
99.8% is whether Social Fetch answered. 98.4% is production lookups that completed without an infrastructure failure. A completed not_found or private is not downtime. Volume and procurement context is on /enterprise.
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 25 platforms?
The uptime measurement is for the public API service. Individual platforms can still return not_found, private, or temporary errors. Coverage is the same catalog as the rest of the product — 25 marketplace platforms and 264 operations.
Prove
Start with 100 free credits
No card. Call a live profile route, keep the requestId, and see the envelope yourself.
support@socialfetch.dev
How to verify
- No card required
- Call a live profile route
- Keep the requestId from the response