Direct answer: the OpenAI Sora API is discontinued
As of November 8, 2026, there is no currently supported OpenAI Sora API to integrate with: OpenAI says the API was discontinued on September 24, 2026. That is separate from third-party services that may use “Sora API” in their product names or documentation; their availability and terms must be checked with those providers. (help.openai.com)
For a new production integration, don’t build against the retired OpenAI API. An API page or code sample that still appears online does not mean the route remains active. OpenAI’s discontinuation notice is the relevant source for the official API’s status. (help.openai.com)
What older Sora API integration examples show
A Pollo AI documentation page describes a Pollo-hosted Sora 2 route—not an OpenAI endpoint. Its captured request example uses POST https://pollo.ai/api/platform/generation/sora/sora-2, an x-api-key header, and Content-Type: application/json. The sample body includes an input object with image, prompt, and aspectRatio, plus webhookUrl and clientSource.
Those details can help identify what that provider documented, but they are not instructions for accessing OpenAI’s discontinued API, and the captured material does not establish that the Pollo route is currently available. The sample uses placeholders; it does not fully explain which input fields are required for each mode or the accepted image formats and aspect ratios. See the linked Pollo documentation in the sources list.
What the documented response does—and doesn’t—tell you
The captured Pollo documentation shows an initial response with a taskId and a status; its listed statuses are waiting, succeed, failed, and processing. It also lists HTTP statuses 400, 401, 403, 404, 429, and 500.
That is not a complete video-generation workflow. The captured documentation does not show a task-status lookup route, webhook contract, completed-video response, or download instructions. Don’t invent a polling or retrieval step from the presence of a task ID. Confirm the current provider documentation covers the entire flow before building against a third-party route.
Availability and capability claims: keep the provider attached
Third-party model pages and API documentation describe Sora 2 capabilities, but such descriptions do not prove that an API route is active or that every described capability is available through it. For example, the captured Pollo page describes text-, image-, and reference-image-based generation, while Together AI’s page says Sora 2 is not available on Together’s Serverless API. These statements concern different providers and should not be combined into one universal Sora API specification.
OpenAI’s developer resource page still lists Sora-related materials, but its Sora 2 prompting guide is explicitly marked archived and may reference outdated models or APIs. Historical documentation is useful context—not evidence that the discontinued API can still be used. (developers.openai.com)
Practical next step
If you are replacing an existing integration, first identify which provider actually served your requests: OpenAI or a third party. For OpenAI, plan around the published discontinuation date; for a third-party service, verify its current availability, endpoint, supported inputs, complete task-to-download workflow, and pricing directly with that provider before committing. OpenAI’s notice says the API ended on September 24, 2026. (help.openai.com)
Sources
What to know about the Sora discontinuation — OpenAI Help Center
Video generation resources — OpenAI Developers
Sora 2: Prompting Guide — OpenAI Developers (archived)