Get an export
Account and platform
Get an export
Fetch one export by id; 404 export_not_found if it is not visible.
GET
Get an export
Fetch one export by id; 404
export_not_found if it is not visible.
Once status is succeeded the response carries bytes, counts
and a downloadUrl pointing at GET /v1/exports/{id}/download (an
authenticated stream of the document). An export owned by another member is a
404, never a leak; admin keys see the whole org.
Authorization
This route requires theread scope.
A missing or invalid credential returns 401 authentication_error. A valid credential without the scope returns 403 permission_denied, and the problem body names the exact scope required.
Headers
These are request conventions the contract does not declare as parameters, so they do not appear in the schema tables below.Success responses
Errors
Beyond the shared statuses, this route can answer with
export_not_found. Every problem body names its own code, and the type URI always resolves to the matching page.
Every error is an RFC 9457 application/problem+json body carrying a stable code, a requestId, and a suggestedAction where Exo has one. See Errors.Authorizations
An Exo API key (exo_...) sent as the X-Exo-API-Key header.
Path Parameters
The export id returned by POST /v1/exports.
Response
Successful Response
One export job (spec 4.11).
status follows the same pending | running | succeeded | failed | canceled vocabulary as Job (documented as a string, not a closed enum,
so a future internal status never breaks a tolerant reader). downloadUrl,
bytes and counts are null until the export succeeds.
What the finished document contains. Null until the export succeeds.