Video Trimmer API - Trim Video by Start and End Time: Pricing, Documentation

by Pixazo

Video Trimmer API returns just that span as a clean H.264/AAC MP4. The cut is re-encoded rather than stream-copied, so it lands exactly where you asked instead of snapping to the nearest keyframe.

Get API Key
Video Trim API

Models Version

WELCOME BONUS

Get $5 Free Credit on First Payment

No strings attached — add funds and get $5 bonus instantly

Claim Your $5 →

Video Trim 1.0 API Documentation

https://gateway.pixazo.ai/media-tools/v1/video-trim

Authentication

All requests require an API key passed via header.

Pricing: Billed at $0.002 per second of the trimmed clip you keep (not the source length) — so cutting a 7-second clip out of a 60-second video costs $0.014, not $0.12.

Rounding: billing is per second but always rounds up to a whole second — a 5.06-second source bills as 6 seconds. The shortest billable job is 1 second.

Retries: this is an asynchronous job on shared encoding capacity, so a request can occasionally come back processing_failed or take much longer than usual. These are transient and succeed on a retry, and a failed job is never charged — the wallet hold is released. If you chain these tools, retry a failed step rather than failing the whole pipeline.

HeaderTypeRequiredDescription
Ocp-Apim-Subscription-KeystringYesYour API subscription key

Video Trim generate request

Request Code

POST https://gateway.pixazo.ai/media-tools/v1/video-trim
Content-Type: application/json
Cache-Control: no-cache
Ocp-Apim-Subscription-Key: YOUR_API_KEY

{
  "video_url": "https://api-assets.pixazo.ai/media-api-test/t.mov",
    "start_seconds": 5,
    "end_seconds": 12
}
import requests

url = "https://gateway.pixazo.ai/media-tools/v1/video-trim"
headers = {
    "Content-Type": "application/json",
    "Cache-Control": "no-cache",
    "Ocp-Apim-Subscription-Key": "YOUR_API_KEY"
}
data = {
    "video_url": "https://api-assets.pixazo.ai/media-api-test/t.mov",
    "start_seconds": 5,
    "end_seconds": 12
}

response = requests.post(url, json=data, headers=headers)
print(response.json())
const url = "https://gateway.pixazo.ai/media-tools/v1/video-trim";
const headers = {
  "Content-Type": "application/json",
  "Cache-Control": "no-cache",
  "Ocp-Apim-Subscription-Key": "YOUR_API_KEY"
};
const data = {
  "video_url": "https://api-assets.pixazo.ai/media-api-test/t.mov",
    "start_seconds": 5,
    "end_seconds": 12
};

fetch(url, {
  method: "POST",
  headers: headers,
  body: JSON.stringify(data)
})
.then(response => response.json())
.then(data => console.log(data));
curl -X POST "https://gateway.pixazo.ai/media-tools/v1/video-trim" \
  -H "Content-Type: application/json" \
  -H "Cache-Control: no-cache" \
  -H "Ocp-Apim-Subscription-Key: YOUR_API_KEY" \
  --data-raw '{
    "video_url": "https://api-assets.pixazo.ai/media-api-test/t.mov",
    "start_seconds": 5,
    "end_seconds": 12
  }'

Output

{
  "request_id": "media-trim_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "status": "QUEUED",
  "polling_url": "https://gateway.pixazo.ai/v2/requests/status/media-trim_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
}

Webhook (Optional)

Add the X-Webhook-URL header to your generate request to receive a POST callback instead of polling.

X-Webhook-URL: https://your-server.com/webhook/callback

Request Parameters - Video Trim generate request

Parameter Required Type Default Allowed values / range Description
video_urlYesstringHTTP(S) URL; ≤ 500 MB, ≤ 600 sPublicly reachable HTTP(S) URL of the source video.
start_secondsNonumber00 – 86400Where the kept clip begins, in seconds from the start of the source. Must be a number — a quoted string is rejected.
duration_secondsConditionalnumber0.1 – 120How much to keep, measured from start_seconds. Takes precedence over end_seconds if both are sent.
end_secondsConditionalnumber0 – 86400; greater than start_secondsWhere the kept clip ends. Give this or duration_seconds; omit both to keep everything from start_seconds to the end of the source. A value at or below start_seconds is ignored rather than rejected, so you get everything from start_seconds onwards. Keep the span you ask for (end_seconds minus start_seconds) within 120 s — the same ceiling duration_seconds enforces.

Example Request

{
  "video_url": "https://api-assets.pixazo.ai/media-api-test/t.mov",
    "start_seconds": 5,
    "end_seconds": 12
}

Response

{
  "request_id": "media-trim_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "status": "QUEUED",
  "polling_url": "https://gateway.pixazo.ai/v2/requests/status/media-trim_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
}

Request Headers

Header Value
Content-Typeapplication/json
Cache-Controlno-cache
Ocp-Apim-Subscription-KeyYOUR_API_KEY

Response Handling

Common status codes.

CodeMeaning
202Accepted — Request queued
Bad Request
401Unauthorized
402Insufficient Balance
403Forbidden
Too Many Requests
500Internal Server Error

Error Responses

Queue system errors and model validation errors.

Queue System Errors

// 402 — Insufficient balance
{
  "error": "Insufficient Balance",
  "message": "Your wallet does not have enough balance."
}
// 400 — Model not found
{
  "error": "Model not found",
  "message": "Model 'media-trim' not found or is disabled"
}

Error via Status/Webhook

{
  "request_id": "media-trim_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "status": "ERROR",
  "model_id": "media-trim",
  "error": "Description of the error",
  "output": null
}

Retrieving Results

Poll the universal status endpoint to check progress and retrieve results.

Endpoint

GET https://gateway.pixazo.ai/v2/requests/status/{request_id}
Ocp-Apim-Subscription-Key: YOUR_API_KEY

cURL Example

curl -H "Ocp-Apim-Subscription-Key: YOUR_API_KEY" \
  "https://gateway.pixazo.ai/v2/requests/status/media-trim_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"

Response (Completed)

{
  "request_id": "media-trim_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "status": "COMPLETED",
  "model_id": "media-trim",
  "error": null,
  "output": {
    "media_url": [
      "https://pub-582b7213209642b9b995c96c95a30381.r2.dev/v1/media-trim_019dxxxx/output.mp4"
    ],
    "media_type": "video/mp4"
  },
  "created_at": "2026-03-31T10:00:00.000Z",
  "updated_at": "2026-03-31T10:00:15.000Z",
  "completed_at": "2026-03-31T10:00:15.000Z"
}

Response Fields

FieldTypeDescription
request_idstringUnique request identifier
statusstringQUEUED, PROCESSING, COMPLETED, FAILED, or ERROR
model_idstringModel that processed the request
errorstring|nullError message if failed
output.media_urlarrayURLs to generated media (R2 CDN)
output.media_typestringMIME type of the output
created_atstringWhen request was created
completed_atstringWhen request completed
polling_urlstringStatus URL (initial response only)

Status Values

StatusDescription
QUEUEDRequest accepted, waiting to be processed
PROCESSINGBeing processed by the model
COMPLETEDDone — output contains the result
FAILEDFailed — check error field
ERRORSystem error — not charged

Status Flow

QUEUED → PROCESSING → COMPLETED
                    → FAILED
                    → ERROR

Typical Workflow

  1. Send a generate request to the API endpoint
  2. Save the request_id from the response
  3. Poll every 5-10 seconds: GET /v2/requests/status/{request_id}
  4. When status is "COMPLETED", download from output.media_url

Tip: Use X-Webhook-URL header to get a callback instead of polling.

Video Trim 1.0 API Pricing

Your request will cost $0.002 per second of the trimmed clip you keep, not the source.
cutting a 7-second clip out of a 30-second video costs $0.014

⚡ Performance

Live usage measured on Pixazo's gateway, split by model version. Generation time is how long a generation takes end-to-end (lower is better). Success rate is the percent of generations that complete (higher is better).

Show data for the last
Generations
11,600last 30d
~387 per day
Success rate
72.4%
of completed generations
Generation time
27.2savg
p95 32.6s
Requests
Jul 16max 4,500Aug 14
Video Trim 1.0Avg 387/day
Generation Time
Jul 16max 27.5sAug 14
Video Trim 1.0Avg 27.2s
Error Rate
Jul 16max 85.7%Aug 14
Video Trim 1.0Avg 27.6%

〰 Uptime

Percent of generations that succeeded over the selected period, per model version.

Avg. Success Rate (30d)
72.41%
across all generations of this model family
Uptime
Jul 16max 100%Aug 14
SuccessfulAvg 72.41%