Changelog

This changelog tracks API behaviour changes. Documentation-only updates are recorded in the project's git history but not here.

Entries are reverse chronological. Each entry is dated and describes any change to request shape, response shape, status codes, or default behaviour.

2026-09-29

POST /v2/movies accepts a movie JSON of up to 2 MB. Before, requests above roughly 200 KB of JSON failed with 500 Error creating movie: Item size has exceeded the maximum allowed size. A body over 2 MB now gets 413 with "code": "movie_json_too_large" and a message that states the limit. See Create movie → Size limit.
POST /v2/movies can answer 500 with "code": "movie_json_not_stored" when the movie could not be saved. Nothing is created or charged; retry.
GET /v2/movies list mode: a page can hold fewer movies than limit while has_next is true, when the movies' json would make the response too large. Keep paging with next_token until has_next is false. See Pagination.
GET /v2/movies list mode now leaves json out with format=simple for new movies (the list used to ignore format). Some older movies still include it.

New output destination: Amazon S3 ("type": "aws-s3"). Save a bucket, its region and the access key of an IAM user in Dashboard → Connections → Output destinations, then reference it in exports[].destinations as { "type": "aws-s3", "id": "<connection id>" }. The movie may set only remote-path and file; the bucket, the region and the keys always come from the saved destination. The destination's Test writes json2video-test.txt to the bucket and leaves it there. See Amazon S3 delivery.
aws-s3 destinations are now delivered. They used to be skipped with aws-s3 destinations are not supported yet. Nothing was delivered. An aws-s3 destination without id, or with other fields than remote-path and file, is now an error in destinations_result.
POST /v2/movies now refuses a movie whose exports[].destinations[] carry AWS keys: HTTP 400, "code": "aws_keys_in_movie". See Errors.

Documentation overhaul. No API behaviour change.
Deprecated: the template element type inside an element list. The behaviour still works at runtime, but it will be removed in a future release. Replace template elements with either a component (for reusable visual blocks) or a movie-level template reference loaded from a saved template.