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.
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
Response Body
application/json
application/json
curl -X GET "https://example.com/v1/files/string"{ "id": "string", "object": "file", "form_id": "string", "response_id": "string", "filename": "string", "mime": "string", "size_bytes": 0, "created_at": 0, "download_url": "string", "download_expires_at": 0}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 respondent's uploaded file, inline
The file's bytes in the JSON body under the same API key: UTF-8 text for text types, base64 otherwise. For a caller that cannot fetch `download_url`. Files over 4 MB answer 413; use `download_url` for those.