Veevid — AI video, image & audio API

One API key for everything on veevid.ai: video generation, image generation and editing, speech, music, transcription and video tools. Every model is called through the same endpoint, POST /api/generate-video, with a mode (the model) and a generation_type (the task).

Setup

1. Get an API key at veevid.ai/settings/api-keys
2. Save it:

mkdir -p ~/.config/veevid
echo "vv_sk_your_key" > ~/.config/veevid/api_key

All requests send Authorization: Bearer $(cat ~/.config/veevid/api_key). Base URL: https://veevid.ai.

Workflow

1. Pick the model with the picker below, then open the matching reference file and find the model's section (search for ### `<mode>` ). It lists every param with allowed values and defaults, the input files, upload folders, rules and an example body. Don't guess params.
2. Quote and confirm — always, before generating. POST /api/quote with the body you will generate with, including the prompt (some models check it). The quote endpoint does not read video URLs and does not always count the images array, so describe input files with the quote fields the model's rules ask for (input_image_count, has_video_input, input_video_count, input_video_duration, …; see api-reference.md). File URLs are not needed to quote, except the audio URL for scribe-v2 and veed-clean-audio — for those, ask the user before uploading the file to price it. Declare real input lengths (input_video_duration, input_audio_duration, …): if they are too low, some models charge the difference after the job. Tell the user the model and the exact required_credits, and wait for a yes. If sufficient is false, offer a cheaper option or veevid.ai/pricing.
3. Upload local files after the user says yes: POST /api/storage/upload with file and the model's upload folder (veed-clean-audio uses /api/storage/presign-upload). Public https URLs can be passed directly unless the model's rules say the file must be uploaded to Veevid.
4. Generate with the confirmed params: POST /api/generate-video → {"generation_id": "vg_…", "status": "processing"}.
5. Poll GET /api/video-generation/{generation_id}/status every 5–10 s until completed or failed. The result is in video_url for every media kind (video, image or audio); multiple images are in result_images. Videos take about 1–3 minutes, images and audio seconds to a minute.

KEY=$(cat ~/.config/veevid/api_key)
BODY='{"mode":"veo3","generation_type":"text-to-video","prompt":"A golden retriever running through sunflowers, cinematic","video_quality":"standard","aspect_ratio":"16:9"}'
curl -X POST https://veevid.ai/api/quote -H "Authorization: Bearer $KEY" -H "Content-Type: application/json" -d "$BODY"
# → {"required_credits":<n>,"current_balance":<n>,"sufficient":true}
# STOP: tell the user the model and <n> credits, and only continue after they say yes.

curl -X POST https://veevid.ai/api/generate-video -H "Authorization: Bearer $KEY" -H "Content-Type: application/json" -d "$BODY"
# → {"generation_id":"vg_abc123","status":"processing",...}

curl https://veevid.ai/api/video-generation/vg_abc123/status -H "Authorization: Bearer $KEY"

Prompts are sent to the model as-is — the website's automatic prompt translation is not applied to API calls. Write prompts in English (translate the user's request yourself).

Model picker

Prices depend on duration, resolution and tier — never quote from memory, always call /api/quote.

Getting files from chat

If the user refers to an image, video or audio file they sent in the conversation but no URL reached you, look through their recent messages for attachments from that same user, show which file you picked (quote or reply to that message) and ask them to confirm before uploading. When several files are needed (start/end frames, reference images), ask which ones and in what order.

Other endpoints

• GET /api/credits → {"success": true, "credits": <n>, "balance": <n>}
• GET /api/user/creations?page=1&pageSize=20&includeAudio=1 — the user's past generations
• POST /api/video-generation/{id}/upgrade-draft — upgrade a Seedance 2.5 480p draft to 1080p. It spends credits: quote it with {"draft_upgrade_id": "<id>"} and get the user's confirmation first, like any generation

Details, response fields and every error code: references/api-reference.md.

Errors

A failed status includes error_message; credits are normally refunded automatically.