Video Processing API Documentation

Authentication

API Key is required for all requests

Each registered user receives a unique API key. Include this key in the Authorization header of your requests.

Endpoint Details

POST /video_processing_api

Request Payload

{
    "URLs": [
        "https://example.com/image1.jpg",
        "https://example.com/image2.jpg"
    ],
    "resolution": "hd",
    "background_music": {
        "url": "https://example.com/music.mp3",
        "volume": "normal"
    },
    "voiceover": {
        "url": "https://example.com/voiceover.mp3",
        "volume": "normal"
    }
}

Response

{
    "status": "processing",
    "job_id": "123456",
    "estimated_duration": 10,
    "total_images": 2,
    "urls": ["https://example.com/image1.jpg", "https://example.com/image2.jpg"],
    "resolution": "hd",
    "check_status_after": 60
}

Make.com Integration

POST Request Setup (json2screen)

Use custom Make.com module: json2screen
Configure with API endpoint URL
Add Authorization header with API key
Map input fields to JSON payload
Prepare URL list, music, and voiceover details

Tip: Ensure all required fields are mapped correctly

Status Check (json2screen check status)

Use custom Make.com module: json2screen check status
Input the job_id from initial request
Configure to retrieve processing status
Handle different status responses
Set up logic for completed or ongoing jobs

Tip: Implement retry mechanism for pending jobs

Error Handling

Status Code	Description
400	Bad Request (No URLs, Invalid Data)
401	Unauthorized (Invalid API Key)
500	Internal Server Error