What you’ll have at the end: a document uploaded through the API and its extracted values back as structured JSON, plus the fileId you need for every other guide.
You need: a fileAI workspace and an API key. Workspace admins create keys in the fileAI app. Keys only work on the instance that issued them.
1

Set your key and base URL

Using a regional instance? Swap the host. See Regions.Check the connection:
Response
2

Request an upload URL

fileAI uploads go straight to storage. First ask for a presigned URL:
Response
3

Upload the file

PUT the raw bytes to presignedUploadURL. The URL expires after 5 minutes.
Processing starts automatically once the upload lands.
4

Track processing

Poll the upload until its steps complete, or skip polling by passing a callbackURL when you request the upload (processing callbacks). Async jobs compares the two.
The response lists each processing step in statuses and the resulting documents in files. Note the fileId of your document.
5

Read the structured values

Response (trimmed)
formValues holds one entry per AI Schema, each with its fields: the field’s title, type and extracted value. Data types explains each value shape. To see where a value came from on the page, see Citations and validations.

Next steps

Shape the output with AI Schemas

Define exactly which fields you want, across one file or many.

Large files and batches

Multipart uploads, batch registration and ZIP archives.

Extract without storing

One-shot extract, split and classify jobs.

Authentication and regions

API keys, regional base URLs and request conventions.