The Toast API
Where to find Toast's OpenAPI contract and the notes for integrators.
Every Toast client (the web app, the desktop app, iOS and Android) uses the same API at https://api.toast.video/v1. This page points you to its contract; it does not repeat it.
The OpenAPI contract
The contract is an OpenAPI 3.1 document, generated from the same schemas the server validates with:
- Live:
https://api.toast.video/v1/openapi.json(alsoopenapi.yaml). Public, no sign-in needed: it returns shapes, never data. - In the repository:
apps/api/openapi/openapi.jsonandopenapi.yaml.
As of November 2026 it describes 184 paths and 234 operations: AI editing, audio, projects and jobs, the wallet and credits, story videos (scenes, cast, generation), the asset library, animated (motion) videos, properties, events, the brand kit, the library and the showcase.
The iOS and Android SDKs are generated from it.
What is not in the contract yet
A few routes are live but not yet in the contract, among them settings, /me, sessions, feedback, the stock-media search proxies and the desktop passthrough. Do not read "not in the contract" as "not available"; read the route module.
Integration notes
Each route module in apps/api/src/routes/ opens with a comment written for integrators on another platform: who calls it, how it is authenticated, every endpoint with its status codes, what leaves the device, and the gotchas (idempotency, polling, retention). Read it before you call a surface for the first time.
Authentication
Requests carry a Clerk session token (JWT). Public routes, such as the contract itself and the showcase, need none.
Feature switches
Some surfaces are switched on per account. A surface that is off answers 404 as if it did not exist, and one your account is not on answers 403. Check the surface's access endpoint (for example GET /properties/access) before showing it.