Skip to content

docs

Documentation

Everything you need for the first request, then the full reference.

First request in three steps

  1. 1Create a key in the panel.
  2. 2Send the link you want to read.
  3. 3Read the JSON. Every key is always there; a missing value is null.
curl
curl -X POST https://app.qobilbek.dev/v1/media/extract \
  -H 'X-Api-Key: '"$API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{"url":"https://www.instagram.com/reel/DcMXl1IPNtB/"}'

Interactive API reference

Every endpoint, every field, with a Try it button. Generated from the server, so it can never drift from the code.

Open the reference

Authentication

Authentication

Pass the key in the X-Api-Key header. The full key is shown once, at creation — we only keep its hash. Never put a key in front-end code.

Response shape

Every response has ok. On success the result is in data; on failure it is in error. The error code is machine-readable and never changes; the message is English only and is meant for logs, not for your users.

"ok": true,
"video_id": "D2_IRvuenwg",
"format": "mp3",
"download_url": "https://…"
}
}
"ok": false,
"code": "insufficient_credits",
"message": "Not enough credits",
"request_id": "8e1924fff13b4217adbbc81e98eeee85"
}
}

Response headers

Every successful answer carries X-Credits-Charged, X-Credits-Remaining, X-Charge-Id and X-Request-Id, plus the X-RateLimit-* headers. A request repeated with the same Idempotency-Key returns Idempotent-Replay: true and costs nothing. Each endpoint has one fixed price per request.

Rate limits

Requests are limited per second and grow with the credits you buy. Over the limit you get 429 with a Retry-After header.

Webhooks and signatures

Each delivery carries X-Timestamp and X-Signature = hex(HMAC-SHA256(secret, "<X-Timestamp>." + body)). Verify the signature with your signing secret and reject old timestamps to stop replays.

Products · Pricing