Sora Videos API jobs complete, but MP4 download fails with 403 Files are not accessible.

Hi everyone,

I’m running into a persistent Sora Videos API download issue and wanted to check if this is an entitlement/file-access problem or a current issue with the Sora content endpoint.

The render job itself succeeds, and I can retrieve/list the completed video object, but downloading the completed MP4 fails with:

{ "error": { "message": "Files [file_...] are not accessible", "type": "invalid_request_error", "param": null, "code": null } }

Endpoint failing:

curl -L "https://api.openai.com/v1/videos/VIDEO_ID/content?variant=video" \ -H "Authorization: Bearer $OPENAI_API_KEY" \ --output video.mp4

I also tried:

curl -L "https://api.openai.com/v1/videos/VIDEO_ID/content" \ -H "Authorization: Bearer $OPENAI_API_KEY" \ --output video.mp4

What works:

• POST /v1/videos creates the Sora job successfully

• GET /v1/videos/{video_id} returns the completed job successfully

• GET /v1/videos?limit=5&order=desc lists the completed video successfully

• The job reaches status: completed, progress: 100, and has a future expires_at

What fails:

• GET /v1/videos/{video_id}/content?variant=video

• GET /v1/videos/{video_id}/content

I tested this with a minimal 4-second Sora job:

• model: sora-2-pro

• size: 720x1280

• seconds: 4

• prompt: simple voice-led canary, no references/assets

• I also tested the hidden file ID from the error against the Files API:

curl "https://api.openai.com/v1/files/file_0000000056507285b63c977fa5a51906" \ -H "Authorization: Bearer $OPENAI_API_KEY"

That returns 404 No such File object, while the video content endpoint returns 403 Files […] are not accessible.

To rule out local request issues, I tested with:

* Node fetch

* direct curl

* /content

* /content?variant=video

* explicit OpenAI-Project header

* Accept: video/mp4

All fail the same way.

I also tested a separate OpenAI project/API key under the same org and a separate key under a different org; both completed rendering but failed on content download with the same Files […] are not accessible error. So this does not look like a single API key, single project, prompt, duration, or resolution issue.

Can you confirm whether completed Sora video content downloads are currently available for this project/org, or whether there is a known issue with the /v1/videos/{video_id}/content file resolver?

Any help appreciated.