For the complete documentation index, see llms.txt. This page is also available as Markdown.

GET /exports/{id}

Poll this endpoint until export status is completed or failed.

Poll an export job until status is completed or failed. When complete, the response includes exportUrl.

Get export status

get

Retrieves the current status of an export job. Poll this endpoint until status is "completed" or "failed".

Authorizations
X-API-KEYstringRequired

API key for authentication

Path parameters
idstringRequired

The unique export ID returned from the export endpoint

Example: abc123xyz
Responses
200

Export status retrieved successfully

application/json
exportAsstring · enumRequired

The requested export format, echoed from the request. Always present — pinned from the original request, so it's returned for every status (pending, completed, and failed).

Example: pdfPossible values:
exportIdstringRequired

Unique identifier for the export job.

Example: abc123xyz
statusstring · enumRequired

Current status of the export job. Poll until "completed" or "failed".

Example: completedPossible values:
gammaIdstringRequired

Canonical file ID of the exported Gamma. Always present. Always the file ID, even when a page/doc ID was supplied as gammaId in the export request (it resolves to its parent gamma), so this may differ from the value you passed.

Example: 9xJZ8QmN2
exportUrlstringOptional

URL to download the exported file (when completed). The file format matches exportAs: pptx → .pptx, pdf → .pdf, png → a .zip archive containing one PNG per card (not a single PNG file). Anyone with this URL can download the file until it expires (about one week) — access is not tied to your API key. Treat the link as a secret: don't log it, share it, or embed it in client-side code.

Example: https://gamma.app/export/abc123.pdf
get/v1.0/exports/{id}

Export URLs expire after approximately one week. Anyone with the URL can download the file; access is not tied to your API key. Treat export links as secrets — do not log them, share them, or embed them in client-side code.

Last updated

Was this helpful?