Status and performance
Live health and measured latency and success rates per endpoint. Numbers are regenerated from request logs, never written by hand.
Live health
Health comes from scheduled checks with known public inputs. Where there is enough traffic, the share of real requests that succeeded in the last hour is shown next to it.
Staging measurements, not production. These numbers come from requests to our staging environment, not from production traffic.
| Endpoint | Status | Live | p50 | p95 | Success rate | Requests measured |
|---|---|---|---|---|---|---|
| Facebook Post API | Beta | — | — | — | — | |
| Facebook Ad Library Search API | Beta | — | — | — | — | |
| Facebook Video Transcript API | Beta | 1,517 ms | 2,437 ms | 65.3% | 26 | |
| Instagram Post API | Beta | — | — | — | — | |
| Instagram Posts API | Beta | — | — | — | — | |
| Instagram Profile API | Beta | — | — | — | — | |
| Instagram Reels Transcript API | Beta | 4,125 ms | 9,203 ms | 98.1% | 53 | |
| Rumble Comments API | Beta | — | — | — | — | |
| Rumble Video API | Beta | — | — | — | — | |
| Rumble Channel Videos API | Beta | — | — | — | — | |
| Rumble Channel API | Beta | — | — | — | — | |
| Rumble Search API | Beta | — | — | — | — | |
| Rumble Transcript API | Beta | — | — | — | — | |
| Threads Profile API | Beta | — | — | — | — | |
| TikTok Comments API | Beta | — | — | — | — | |
| TikTok Post API | Beta | — | — | — | — | |
| TikTok Posts API | Beta | — | — | — | — | |
| TikTok Profile API | Beta | — | — | — | — | |
| TikTok Transcript API | Beta | 668 ms | 2,705 ms | 99.1% | 112 | |
| YouTube Comments API | Beta | — | — | — | — | |
| YouTube Video API | Beta | — | — | — | — | |
| YouTube Channel Videos API | Beta | — | — | — | — | |
| YouTube Channel API | Beta | — | — | — | — | |
| YouTube Transcript API | Beta | 511 ms | 989 ms | 96.5% | 29 |
“—” means the endpoint had too few requests in the window to publish a number.
How these numbers are measured
- Which requests. Requests to our staging environment over the last 7 days: customer requests plus our own scheduled checks, which call every endpoint with known public inputs. Load tests are left out, and so are cache hits and requests turned away before any work was done (
unauthorized,forbidden,insufficient_credits,spend_limit_reached,rate_limited,method_not_allowed,endpoint_retired,idempotency_key_reused,idempotency_key_in_progress,job_not_foundandunknown_endpoint). - What counts as success. Any correct answer. A request fails when the platform or SocialTap could not produce one (
upstream_blocked,upstream_errorandinternal), or when a scheduled check got a wrong answer. Errors that correctly describe the request or the item (invalid_input,invalid_cursor,not_found,private_or_unavailable,no_transcriptandoverloaded) count as successes: the API did its job. - Latency. p50 and p95 are the time SocialTap took for successful (HTTP 200) responses: half of the requests were faster than p50, 95% faster than p95.
- Sample size. Each row shows how many requests it is based on; endpoints with too few requests show no numbers.
- Rounding. Success rates are rounded down, so 99.96% shows as 99.9%, never 100%.
Failed requests are never charged, whatever the success rate.