API

The REST API makes and fetches videos from your own code. It uses the same studios, prices and credits as the app. Base URL: https://clickpop.ai/api/v1. Requests and responses are JSON.

Authentication

Create a key on the API keys page. The full key is shown once; we keep only a hash, so a lost key can be revoked and replaced but not recovered. Keep it on your server and send it on every request:

Authorization: Bearer YOUR_API_KEY

Calls that spend credits need a plan on the account.

How a render works

• Add "dry_run": true to see the price without rendering or spending anything.
• Without it, the call holds the credits and answers 202 with a video whose status is processing.
• Poll GET /videos/{id} every few seconds. When status is succeeded, download url. On failed, the credits are already returned and error says why.

POST /videos takes prompt (required), seconds (default 5), resolution (480p, 720p or 1080p; default 480p), model (default auto) and an optional character_id.

Quickstart

# 1. Price it first: nothing renders, nothing is charged
curl -X POST https://clickpop.ai/api/v1/videos \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"prompt":"A barista slides a latte across the counter, slow motion","seconds":5,"dry_run":true}'

# 2. Start it: 202 with a video in "processing"
curl -X POST https://clickpop.ai/api/v1/videos \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"prompt":"A barista slides a latte across the counter, slow motion","seconds":5}'

# 3. Poll until status is "succeeded", then download url
curl https://clickpop.ai/api/v1/videos/VIDEO_ID -H "Authorization: Bearer YOUR_API_KEY"

Endpoints

All paths are under https://clickpop.ai/api/v1.

Errors

Errors come back as JSON with an error field that says what went wrong.