Skip to content
takeai

Request access to this video?

This account doesn't have access. You can ask the owner to invite your signed-in email.

Delete this video forever?

Its edit and source file are erased from every device. This can't be undone.

Delete the folder “”?

Its videos and folders move up to All videos. No video is deleted.

Navigate

Home
All videos
Starred
Shared with me
Trash
In progress
Ready to post
Account
Help

Actions

Upload a video
Send feedback
Sign out

Settings

Docs

Take videos from recording to finished cut with the public API, the CLI, or an AI assistant.

Start with a personal key

Create a key under CLI / MCP, copy it once, and store it as TAKEAI_API_KEY. Base URL: https://usetake.ai/api/v1. Send Authorization: Bearer YOUR_API_KEY on every private request.

Check your account and list videos
curl https://usetake.ai/api/v1/account \
  -H "Authorization: Bearer $TAKEAI_API_KEY"

curl https://usetake.ai/api/v1/projects \
  -H "Authorization: Bearer $TAKEAI_API_KEY"

A key uses your account’s permissions, sharing roles, plan, and editing allowance. It can upload, edit, export, share, and delete videos. It cannot change billing, credentials, or delete the account. Revoke it under CLI / MCP to stop future requests.

Upload, wait, download

  1. POST /uploads with the file name, size, and an intent. The response includes id, chunk_bytes, and received.
  2. Send each file in chunks no larger than chunk_bytes to PUT /uploads/UPLOAD_ID/takes/0?offset=0. GET /uploads/UPLOAD_ID reports what arrived, so an interrupted upload can resume.
  3. POST /uploads/UPLOAD_ID/complete creates the video. Repeating it returns the same project.
  4. Poll GET /projects/PROJECT_ID until status is ready, or stream GET /projects/PROJECT_ID/events.
  5. Download GET /projects/PROJECT_ID/media/output once it is ready.

Download a complete Python upload example.

Edit with AI or the timeline

Ask the AI editor
curl "https://usetake.ai/api/v1/projects/PROJECT_ID/assistant" \
  -H "Authorization: Bearer $TAKEAI_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"message":"Tighten the intro and add captions","render":true}'
Read, save and render a timeline
# Fetch the current document and revision before changing the timeline.
curl "https://usetake.ai/api/v1/projects/PROJECT_ID/edit" \
  -H "Authorization: Bearer $TAKEAI_API_KEY"

# Save {"revision":CURRENT_REVISION,"document":{...}}.
curl -X PUT "https://usetake.ai/api/v1/projects/PROJECT_ID/edit" \
  -H "Authorization: Bearer $TAKEAI_API_KEY" \
  -H "Content-Type: application/json" --data-binary @edit.json

curl -X POST "https://usetake.ai/api/v1/projects/PROJECT_ID/edit/render" \
  -H "Authorization: Bearer $TAKEAI_API_KEY"

Read document and revision first, keep the fields you are not changing, and save both. A stale revision returns 409. Saving creates a revision; rendering exports it.

Errors and retries

Errors return {"error":"What needs to change"}. 401 means the key is missing or revoked, 403 means access is refused, 404 means it is not visible to this account, and 409 means a revision or upload conflict. For 429 and 503, honor Retry-After. Keep keys on your machine. Do not put them in public browser code.

Download the OpenAPI reference for every endpoint.