revoltAPI PLATFORM
All systems nominal Read docs
THE DEVELOPER TOOLKIT v1.3

Less glue code.
More shipped.

A documented REST API for supported public media extraction and link resolution, with one interactive playground and persistent usage telemetry.

REST-style routes JSON responses No API key required
R
API / LIVE
revolt.biz.id
response.json200 OK
{
  "status": true,
  "creator": "Revolt API",
  "service": "tiktok",
  "result": {
    "available": true
  }
}
0 API requests
0 Successful
0 Errors
0 Active IP blocks
LIVE TELEMETRY

Real usage. Live numbers.

Counts persist in Neon PostgreSQL across Vercel instances. Documentation, health checks, and telemetry polling are excluded.

Updating every 3 seconds
REQUEST VOLUME

Last 30 minutes

LIVE
0requests in the visible window0 errors
30 min ago15 minNow
Process uptime—Blocked requests0
REQUEST LOG

Recent API activity

Waiting for data
EndpointResultHTTPLatencyTime
No requests recorded yet. Try an endpoint to populate this panel.
Privacy-minded telemetry: source URLs, query strings and raw client IP addresses are not displayed.
THE TOOLBOX

Endpoints, without the hunt. 28 routes

Browse the reference, inspect accepted domains and response formats, then send a request from the playground.

View raw endpoint list
Loading endpoint catalogue
Loading catalogue… Live catalogue from the API
UP AND RUNNING

Three lines.
You're connected.

Every endpoint accepts a source URL in the url query parameter. Responses include a status flag and the original scraper result.

01

Choose a routeUse the endpoint catalogue above.

02

Pass the source URLEncode the URL as a query parameter.

03

Read the JSONCheck status before using result.

make-your-first-request
curl -G "https://revolt.biz.id/api/downloader/tiktok" \
  --data-urlencode "url=https://www.tiktok.com/@user/video/123456789"
REFERENCE GUIDE

Everything the response tells you.

Predictable request rules, status codes, and examples you can apply in your own client.

Request contract

Use GET and provide one required query parameter: url. The URL must be absolute, public, and use HTTP or HTTPS. Each endpoint enforces its own accepted-domain list.

GET?url=https%3A%2F%2F…

Read the response

Check both the HTTP status and JSON status. Successful responses include result and responseTime. Result fields depend on the upstream provider.

{ "status": true, "result": { … } }

HTTP status codes

400Missing or invalid URL
422Domain not supported
429Rate limit or temporary block
502Upstream extractor failed
504Request timed out

Anti-spam policy

50 API endpoint requests inside a rolling 5-minute window triggers an IP block for 30 minutes. Health, documentation and metrics polling are excluded from this counter.

50 requests5 minutes30-minute block

Client examples

Copy the quickstart code for cURL, browser JavaScript, or Python. Always use a timeout, handle non-2xx responses, and avoid retry loops that can trigger abuse protection.

Open quickstart

Reliability notes

This API depends on third-party extractors. A supported URL may temporarily fail if the source, extractor, or network is unavailable. Output fields are not guaranteed to be identical across providers.

System status
TRY IT YOURSELF

A live request, right here.

Use a public link you have permission to access. This sends a real request to the current API.

Live playground
01
Build requestConfigure your endpoint
i Public links only. Some providers may be temporarily unavailable.
GET/api/downloader/tiktok?url=…
02
ResponseJSON payload
Waiting
STATUS —TIME —
Waiting for your first request…
No request sentJSON
Built on third-party providers

Availability and returned media depend on the source platform and extractor. Use this API responsibly and only access content you are allowed to use.

Check status Contact developer