Build downloads with Insto

# Available only after support activation
export INSTO_MEDIA_TOKEN="issued-after-review"

curl -X POST https://insto.app/v1/resolve \
  -H "X-API-Key: $INSTO_MEDIA_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"media_source":"https://www.youtube.com/watch?v=VIDEO_ID"}'

Insto presents three practical points for Credential safety. First comes server-side secret storage. The download review then covers no client bundle embedding. Its final point is no public logs or repositories.

{
  "success": true,
  "platform": "youtube",
  "title": "Example video",
  "formats": [
    {"id":"18","type":"video","quality":"360p","container":"mp4"}
  ],
  "cached": false
}

Insto presents three practical points for Format identifier. First comes the returned value unchanged. The download review then covers per-link availability. Its final point is no guessed quality label.

curl -X POST https://insto.app/v1/jobs \
  -H "X-API-Key: $INSTO_MEDIA_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"media_source":"https://www.youtube.com/watch?v=VIDEO_ID","media_variant":"18"}'

curl https://insto.app/v1/jobs/PREPARE_ID \
  -H "X-API-Key: $INSTO_MEDIA_TOKEN"

In Insto, one-second initial wait comes first when explaining Job polling. That download review follows with capped backoff and closes on temporary signed delivery.

{
  "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": "…"
}

• idempotent アプリケーションロジックを使用し、同じユーザークリックに対して重複ジョブを開始しないでください。
• キャッシュはメタデータを簡単に解決しますが、署名されたダウンロード URL は常に有効期限切れとみなします。
• Use bounded exponential backoff with jitter for 429, 503 and retryable errors.
• パブリックメディアまたはアクセス権限があるメディアのみを処理します。DRMやアクセス制御はバイパスされません。
• リクエスト ID とジョブ ID をプライベートの操作ログに保持します。送信された URL を不必要にログに記録しないでください。

For Schema access, Insto begins with activation before exploration. Its download review pairs that with assigned authentication and ends with documented request shapes.