TrySora guide
Sora video generator API: verify the lifecycle before integrating
A product login, ChatGPT subscription, OpenAI API project, and TrySora API key are not interchangeable. Start with the current official endpoint lifecycle before writing integration code.
Official OpenAI documentation reviewed August 27, 2026 marks the Sora API deprecated and schedules permanent shutdown for September 24, 2026. New production dependencies should account for that date and verify the page again before launch.
External product and API facts reviewed August 27, 2026.
What the official API reference currently says
OpenAI documents POST /videos for creating a video job with a prompt and optional image reference. The same reference labels the Sora API deprecated and gives a scheduled permanent shutdown date of September 24, 2026. The model directory also labels Sora 2 and Sora 2 Pro as deprecated.
The page still documents request fields and rate limits, but documentation of an endpoint is not a promise of access for every account. Model permission, usage tier, region, billing, and lifecycle must all be checked in the relevant OpenAI project.
Keep four account boundaries separate
An OpenAI API key belongs to an OpenAI API project. A ChatGPT account or plan does not automatically become an API key. A historical Sora product login is a third surface. TrySora account API keys are issued and governed by TrySora and must not be presented as OpenAI keys.
- OpenAI product access
- ChatGPT account or workspace
- OpenAI API project, key, billing, and model permission
- TrySora account, credits, keys, and configured providers
Migration-ready integration checklist
If you maintain an existing integration, inventory every job creation, polling, download, storage, retry, and error-handling path. Preserve the model ID and provider in task records. Add a controlled fallback only after its quality, cost, policy, and output contract are tested.
TrySora does not guarantee a Sora endpoint. Use its own documented API surface, current settings, and provider model catalogue; never send an OpenAI key to an unrelated field unless the product explicitly documents that integration.
- Recheck the official shutdown notice before release.
- Stop creating new hard dependencies on a deprecated endpoint.
- Test fallback outputs with the same permitted references.
- Keep API secrets server-side and rotate exposed credentials.
Official sources to verify
Product and API lifecycle information changes. Reopen the source before relying on a date, entitlement, model, price, or limit.
- OpenAI API reference: Create video
Official endpoint contract and current deprecation/shutdown notice.
- OpenAI API model page: Sora 2
Official model lifecycle, modality, pricing, and rate-limit page; verify again for changes.
- OpenAI API model page: Sora 2 Pro
Official companion model lifecycle page; verify its current status before relying on it.
Frequently asked questions
Is the Sora API already shut down?
Not according to the wording reviewed August 27, 2026. OpenAI marks it deprecated and schedules permanent shutdown for September 24, 2026; recheck the official page after that date.
Is a ChatGPT login the same as an OpenAI API key?
No. API access, projects, keys, permissions, and billing are separate from a ChatGPT login or plan.
Is a TrySora API key an OpenAI key?
No. TrySora keys belong to this independent service and do not represent an OpenAI credential or model entitlement.
Should I start a new Sora API integration now?
The official deprecation and scheduled shutdown create a material lifecycle risk. Verify the current docs and choose a maintained alternative before creating a new production dependency.