POST /videos/{video_id}?reencode

Reprocesses a single video — the way to encrypt, re-compress or re-segment content that already exists.

⚠️

This operation consumes credits

Insufficient balance returns 402 (not 400), with the number of credits required. Budget for it before reprocessing a catalogue.

📘

Authorization

Requires a valid API token in the Authorization header (without Bearer prefix). The video must belong to the authenticated user.

HTTP Method & Path

POST /videos/{video_id}?reencode

Base URL: https://api-v2.pandavideo.com.br

Authentication Requirements

Path Parameters

Query Parameters

Request Body

Content-Type: application/json

Body Parameters

{ "hls_encryption": true }

📘

These values override the library

compression_mode and hls_segment_duration sent here take precedence over the library configuration for this video.

Response

Success Response (200)

{
  "message": "Reencode request sent to SQS",
  "video_id": "11111111-2222-3333-4444-555555555555"
}

The response confirms the request was queued — reprocessing happens asynchronously.

⚠️

Prerequisite: the original file

The library must have keep_original_files enabled and the video must still have its original file. Otherwise the call fails with 400.

Error Responses

Example Usage

cURL

curl -X POST \
  "https://api-v2.pandavideo.com.br/videos/{video_id}?reencode" \
  -H "Authorization: $PANDA_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "hls_encryption": true }'

Related

• Many videos at once: POST /videos/reencode_bulk
• Check which videos are encrypted: GET /videos/hls_encrypted
• The library switch this applies retroactively: HLS Encryption