Skip to content
OmniscapeRenders API
All pages
  1. Overview
  2. Quick start
  3. Authentication
  4. API reference
    1. GET /media
    2. POST /media
    3. GET /media/{id}/preview
    4. GET /integrations/google/connect
    5. GET /integrations/google
    6. DELETE /integrations/google
    7. GET /integrations/google/folders
    8. POST /media/import
    9. GET /media/imports/{id}
    10. POST /renders
    11. GET /renders/{id}
    12. GET /renders/{id}/download
    13. GET /usage
  5. Code examples
  6. Error handling
  7. Rate limits & quotas
  8. Troubleshooting
  9. Changelog

Reference

GET

/api/v1/renders/{id}/download

Requires the renders:read scope.

The finished MP4. Returns video bytes, not JSON.

Request

curl -s "https://omniscape.io/api/v1/renders/rnd_7ef2da3bde9a/download" \
  -H "Authorization: Bearer $OMNISCAPE_API_KEY" -o render.mp4

Response

HTTP/1.1 200 OK
Content-Type: video/mp4
Content-Disposition: attachment; filename="rnd_7ef2da3bde9a.mp4"
Cache-Control: private, no-store
X-Request-Id: 0f1c…

<binary video data>

Notes

  • This is asset.url from the render. It does not expire — your API key authorises it, not a token in the link — so you can fetch it days later, and you can re-fetch it as many times as you like at no cost.
  • It needs the Authorization header, which means it is not a link you can email to someone or put in a <video> tag. Download the bytes and host or share them yourself.
  • Before the render completes, or if the file is not available, this is 404 asset_unavailable rather than an empty body.

Codes this call can return are on Error handling. If something is behaving unexpectedly, Troubleshooting is organised by symptom.