---
type: AI Model
id: video-merge-api
title: Video Merge API
provider: Pixazo
description: "Join 2 to 6 clips into one video in a single call. Clips are concatenated in the order you send them; when they already share a codec and size the API stream-copies them, which assembles a long timeline in seconds instead of re-encoding it. Mixed sources are normalised to a common format first. MP4/MOV inputs, 150 seconds of combined source."
resource: https://www.pixazo.ai/models/video-merge-api
docs_url: https://www.pixazo.ai/models/video-merge-api
latest_version: v1
tags:
  - video-merger
  - pixazo
variants:
  - id: media-merge-v1
    name: Video Merge 1.0
    version: 1.0
    capabilities:
      - Merge
timestamp: 2026-08-24T14:57:15.247Z
---

# Video Merge API

> Provider: **Pixazo**
> Source: https://www.pixazo.ai/models/video-merge-api

Join 2 to 6 clips into one video in a single call. Clips are concatenated in the order you send them; when they already share a codec and size the API stream-copies them, which assembles a long timeline in seconds instead of re-encoding it. Mixed sources are normalised to a common format first. MP4/MOV inputs, 150 seconds of combined source.

## Video Merge 1.0

### Merge

## Base URL

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

## Authentication

All requests require an API key passed via header.

**Pricing:** Billed at **$0.002 per second of combined video** — the total length of the clips you join. Joining three 30-second clips costs $0.18. Combined source is capped at 150 seconds.

**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.

**Inputs must be MP4 or MOV.** Anything else — WebM, MKV, AVI — is rejected up front with `every video_urls entry must be a readable MP4/MOV`. The reason is billing, not capability: a merge is priced on the SUM of its clips, so every clip’s duration has to be measured before the job is accepted, and that measurement reads the MP4/MOV container only. Rejecting is deliberate — guessing a duration would mis-charge you. Convert other formats with the **Video Converter API** first, then merge.

Header

Type

Required

Description

Ocp-Apim-Subscription-Key

string

Yes

Your API subscription key

## Video Merge generate request

## Request Code

HTTP Python JavaScript cURL

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

{
  "video_urls": [
    "https://api-assets.pixazo.ai/media-api-test/t.mov",
    "https://api-assets.pixazo.ai/media-api-test/t.mov"
  ]
}
```

```
import requests

url = "https://gateway.pixazo.ai/media-tools/v1/video-merge"
headers = {
    "Content-Type": "application/json",
    "Cache-Control": "no-cache",
    "Ocp-Apim-Subscription-Key": "YOUR_API_KEY"
}
data = {
    "video_urls": [
    "https://api-assets.pixazo.ai/media-api-test/t.mov",
    "https://api-assets.pixazo.ai/media-api-test/t.mov"
    ]
}

response = requests.post(url, json=data, headers=headers)
print(response.json())
```

```
const url = "https://gateway.pixazo.ai/media-tools/v1/video-merge";
const headers = {
  "Content-Type": "application/json",
  "Cache-Control": "no-cache",
  "Ocp-Apim-Subscription-Key": "YOUR_API_KEY"
};
const data = {
  "video_urls": [
    "https://api-assets.pixazo.ai/media-api-test/t.mov",
    "https://api-assets.pixazo.ai/media-api-test/t.mov"
  ]
};

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-merge" \
  -H "Content-Type: application/json" \
  -H "Cache-Control: no-cache" \
  -H "Ocp-Apim-Subscription-Key: YOUR_API_KEY" \
  --data-raw '{
    "video_urls": [
    "https://api-assets.pixazo.ai/media-api-test/t.mov",
    "https://api-assets.pixazo.ai/media-api-test/t.mov"
    ]
  }'
```

## Output

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

[Try Now](https://api.pixazo.ai/api-details#api=media-tools&operation=video-merge)

## 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 Merge generate request

Parameter

Required

Type

Default

Allowed values / range

Description

video\_urls

Yes

array of strings

—

2 – 6 items; each an HTTP(S) URL to an **MP4 or MOV**, ≤ 500 MB each; combined length ≤ 150 s

The clips to join, concatenated in the order given. Every entry must be readable — if any one cannot be measured the request is rejected before you are charged, rather than billed on a partial total.

target\_resolution

No

enum

— (matches the first clip)

`480p`, `720p`, `1080p`

Normalise every clip to this size before joining. Omit it and clips that already share a codec and size are **stream-copied**, which assembles a long timeline in seconds instead of re-encoding it.

## Example Request

```
{
  "video_urls": [
    "https://api-assets.pixazo.ai/media-api-test/t.mov",
    "https://api-assets.pixazo.ai/media-api-test/t.mov"
  ]
}
```

## Response

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

## Request Headers

Header

Value

Content-Type

application/json

Cache-Control

no-cache

Ocp-Apim-Subscription-Key

YOUR\_API\_KEY

## Response Handling

Common status codes.

Code

Meaning

202

Accepted — Request queued

400

Bad Request

401

Unauthorized

402

Insufficient Balance

403

Forbidden

429

Too Many Requests

500

Internal 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-merge' not found or is disabled"
}
```

### Error via Status/Webhook

```
{
  "request_id": "media-merge_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "status": "ERROR",
  "model_id": "media-merge",
  "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-merge_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
```

## Response (Completed)

```
{
  "request_id": "media-merge_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "status": "COMPLETED",
  "model_id": "media-merge",
  "error": null,
  "output": {
    "media_url": [
      "https://pub-582b7213209642b9b995c96c95a30381.r2.dev/v1/media-merge_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

Field

Type

Description

request\_id

string

Unique request identifier

status

string

QUEUED, PROCESSING, COMPLETED, FAILED, or ERROR

model\_id

string

Model that processed the request

error

string|null

Error message if failed

output.media\_url

array

URLs to generated media (R2 CDN)

output.media\_type

string

MIME type of the output

created\_at

string

When request was created

completed\_at

string

When request completed

polling\_url

string

Status URL (initial response only)

## Status Values

Status

Description

QUEUED

Request accepted, waiting to be processed

PROCESSING

Being processed by the model

COMPLETED

Done — output contains the result

FAILED

Failed — check error field

ERROR

System 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.