https://quickdl.appBuild downloads with QuickDL
QuickDL lets developers inspect the compact request model ahead of activation. Support must validate the product before a private key and quota become usable.
Quick start
In QuickDL, support-activated credentials comes first when explaining API host. That compact utility follows with an assigned tenant endpoint and closes on a server-only call path.
X-API-Key: pending_activation_…QuickDlJobsv1# Available only after support activation
export QUICKDL_JOB_KEY="issued-after-review"
curl -X POST https://quickdl.app/v1/resolve \
-H "X-API-Key: $QUICKDL_JOB_KEY" \
-H "Content-Type: application/json" \
-d '{"public_link":"https://www.youtube.com/watch?v=VIDEO_ID"}'QuickDL handles Credential safety by first identifying server-side secret storage. It follows with no client bundle embedding and keeps no public logs or repositories in view.
Resolve a link
In QuickDL, source detection comes first when explaining Resolve operation. That compact utility follows with formats from one submitted URL and closes on no invented outputs.
/v1/resolveScope: resolve| Field | Type | Required | Description |
|---|---|---|---|
public_link | HTTPS URL | Yes | Public or authorized media page to analyze. |
tenant | string | No | Assigned tenant domain. Usually omitted. |
{
"success": true,
"platform": "youtube",
"title": "Example video",
"formats": [
{"id":"18","type":"video","quality":"360p","container":"mp4"}
],
"cached": false
}QuickDL handles Format identifier by first identifying the returned value unchanged. It follows with per-link availability and keeps no guessed quality label in view.
Create and follow a download job
QuickDL's compact utility reviews asynchronous preparation for Job creation. It shows a short HTTP request next and does not obscure bounded worker execution.
/v1/jobsScope: jobs| Field | Type | Required | Description |
|---|---|---|---|
public_link | HTTPS URL | Yes | The same normalized source submitted to resolve. |
download_option | string | Yes | An exact ID from the resolve response. |
tenant | string | No | Assigned tenant domain. Usually omitted. |
curl -X POST https://quickdl.app/v1/jobs \
-H "X-API-Key: $QUICKDL_JOB_KEY" \
-H "Content-Type: application/json" \
-d '{"public_link":"https://www.youtube.com/watch?v=VIDEO_ID","download_option":"18"}'quick_job.GET /v1/jobs/{quick_job} with the same key.| Status | Meaning | Client action |
|---|---|---|
queued | Admitted to the bounded queue. | Poll again with backoff. |
extracting | Refreshing source metadata or route. | Continue polling. |
processing | Downloading, remuxing or merging. | Display server progress. |
ready | Signed download is available. | Send the URL to the user. |
failed | Terminal structured error. | Read error_code. Retry only when advised. |
expired | Temporary output was removed. | Create a new job. |
curl https://quickdl.app/v1/jobs/QUICK_JOB \
-H "X-API-Key: $QUICKDL_JOB_KEY"QuickDL presents three practical points for Job polling. First comes one-second initial wait. The compact utility then covers capped backoff. Its final point is temporary signed delivery.
Predictable errors
QuickDL approaches Error contract through one non-2xx envelope, then a support request ID. The compact utility keeps predictable client handling explicit.
{
"success": false,
"error": {
"code": "RATE_LIMITED",
"category": "rate_limited",
"message": "Too many requests. Please try again shortly.",
"retryable": true,
"details": {"retry_after_seconds": 20}
},
"request_id": "…"
}| HTTP | Typical meaning | Action |
|---|---|---|
| 400 | Invalid URL, body or unavailable format. | Correct the request. Resolve again for formats. |
| 401 | Missing, invalid, expired or wrong-scope key. | Check the server-side credential. |
| 403 | Tenant or source policy rejected the request. | Do not bypass the policy. Contact support. |
| 404 | Unknown or expired job. | Create a new job if appropriate. |
| 429 | Request or active-job limit reached. | Honor retry_after_seconds. |
| 503 | Queue/capacity or upstream temporarily unavailable. | Retry with exponential backoff and jitter. |
Operational contract
QuickDL grants a compact, client-specific quota that supports the integration without destabilizing source services.
- Use idempotent application logic and never start duplicate jobs for the same user click.
- Cache resolve metadata briefly, but always treat signed download URLs as expiring.
- Use bounded exponential backoff with jitter for
429,503and retryable errors. - Process only public media or media you are authorized to access. DRM and access controls are not bypassed.
- Keep request IDs and job IDs in private operational logs. Do not log submitted URLs unnecessarily.
In QuickDL, activation before exploration comes first when explaining Schema access. That compact utility follows with assigned authentication and closes on documented request shapes.
Activate through support
Provide QuickDL with the integration name, expected monthly volume and required sources. Identify the operations the server will perform so approval produces a narrowly scoped, one-time key.
Request activation Keys are tenant-scoped, revocable and issued through the Contact form. Anonymous scripts cannot execute downloader work.