Skip to main content
Attachments let you provide source material for a video job. The API accepts up to 100 attachments per job. Each attachment must be a publicly accessible signed URL.

Request shape

Fields

URL requirements

Signed URLs must be reachable by Motion servers without additional headers, cookies, or authentication. Use URLs with enough time to live for ingestion and generation. For long video files, prefer a generous expiry. Local file paths (such as file:///C:/Users/you/video.mp4) are rejected with 400 Invalid request — Motion servers cannot read files on your machine. Upload local files first (see below).

Uploading local files

If your file only exists locally, use POST /uploads to get a signed upload URL, push the bytes, and attach the returned URL:
The response contains upload_url, upload_fields, and attachment_url:
MCP profiles that expose upload_asset use the same flow. Check your connected profile’s tool list before uploading. Size limits by type: video 5 GB, audio 500 MB, images 50 MB. The upload URL is valid for 1 hour; the attachment_url is valid for 7 days. Rate limit: at most 100 uploads per user per 5 hours (429 rate_limited beyond that). Uploaded files are automatically deleted after 14 days — this flow is for attaching source material to Motion jobs, not for file storage.

Limits

  • Maximum attachments per job: 100.
  • Maximum URL length: 4096 characters.
  • Maximum attachment name length: 240 characters.
  • The API rejects more than 100 attachments with 400 Invalid request.