Read a ready export's contents
The export's text, a slice at a time, under the same API key, for a caller that cannot fetch `download_url` (an agent sandbox that only reaches allow-listed hosts, say). Read from `offset` 0 and pass `next_offset` back until it is null; the slices join into the exact file.
A server-side secret key. Never send one from a browser — a request carrying an Origin header is refused for this reason.
In: header
Path Parameters
Query Parameters
0 <= value <= 900719925474099101000 <= value <= 200000200000Response Body
application/json
application/json
application/json
curl -X GET "https://example.com/v1/exports/string/content"{ "id": "string", "object": "export_content", "format": "csv", "offset": 0, "next_offset": 0, "total_bytes": 0, "content": "string"}Check an export and get its download link
Poll until `status` is `ready`, then follow `download_url`. A `failed` export carries the reason in `error`. The link is re-minted on every read, so read again rather than storing one.
A respondent's uploaded file, with a short-lived download link
File-upload answers carry a `fileId`. This resolves one to its metadata and a signed URL that needs no API key, so it is safe to hand to a browser and it expires within minutes.