Skip to main content
PUT
Update File Reading

Update File Reading

Use this endpoint to correct OCR or LLM extraction output before converting the reading into invoices or wastes.

Request

Headers

string
required
Your API key for authenticationExample: sk_live_1234567890abcdef
string
required
Your organization UUIDExample: a8315ef3-dd50-43f8-b7ce-d839e68d51fa

Path Parameters

string
required
File reading UUID from GET /v1/files/readings.

Body

Send the full updated content.items array. The shape depends on the reading category.
object
required
Wrapper for the updated extracted content.
array
required
Updated parsed items. Replace the existing list with the corrected values.

Response

Returns the updated file reading (HTTP 200).
string
File reading UUID.
string
Processing status (e.g. "success").
object
Updated extracted content.

Example

Successful Response

403 Forbidden

Cause: The authenticated user is not a member of the organization

404 Not Found

Cause: The file reading does not exist or belongs to another organization

422 Unprocessable Entity

Cause: Missing required content.items array

Notes

  • Use this before calling POST /v1/files/readings.
  • The API does not currently publish category-specific schemas in the docs, so clients should start from the values returned by GET /v1/files/readings, modify only the needed fields, and send the full content.items array back.

List File Readings

Retrieve readings to get the current content

Create Records

Convert the edited reading into invoices or wastes

Upload Files

Upload new files via presigned S3 URLs

Files Overview

Learn about the Files API