Adaptive export

POST /v1/adaptive builds a downloadable ZIP. Extract its files into your own storage and serve its relative manifests and segments from there. Videxo returns expiring download links for the archive; your application supplies hosting and a player.

curl "$VIDEXO_API_URL/v1/adaptive" \
  -H "Authorization: Bearer $VIDEXO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "input": "https://example.com/video.mp4",
  "manifests": "both",
  "max_resolution": "720p"
}'

const response = await fetch(`${process.env.VIDEXO_API_URL}/v1/adaptive`, {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${process.env.VIDEXO_API_KEY}`,
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    "input": "https://example.com/video.mp4",
    "manifests": "both",
    "max_resolution": "720p"
  }),
});
const job = await response.json();

manifests is hls, dash or both (the default). max_resolution is 720p (the default) or 1080p. The video ladder is 360p, 480p and 720p, with 1080p added for that maximum. Each rendition is H.264 at 30 fps in a 16:9 frame; the source display shape is preserved with black bars. When present, the first audio stream becomes AAC. HLS and DASH share CMAF segments, six seconds each.

The source must fit ten minutes, the job deadline and your plan's input/output limits. The archive is bounded to 1 GB and 600 files. Longer sources are refused, never silently shortened. The job has exactly one input and one adaptive output; additional outputs and transforms are refused.

In POST /v1/jobs, use one output with type: "adaptive", the same options and optional filename: "export.zip". The Job has command: null and lists its processing step. Poll it or receive your completion webhook, then download its sole ZIP output.

Billing uses the existing video rates for every rendition, audio when produced, transferred bytes and processing time. The Playground shows the backend's initial credit hold separately from the expected charge. Without approved packaging-time and archive-size factors, the total estimate stays unknown. The completed Job records actual usage. New named SDK methods are not yet published; use the HTTP examples for this addition.