Skip to main content

Endpoint

Authentication

This endpoint requires an OAuth access token. Send it as a bearer token:
Required scope: sor:read

Path Parameters

Request Body

The body is optional. Send {} (or no body) to use the defaults, which return only the extracted fields.

Request Example

Response

Success Response

Status Code: 200 OK The response is a single document object. This is the same shape returned for each entry in the Search Documents documents array.

Response Fields

Field Value Object

Workflow Metadata Object

Mapped Field Object

Error Responses

400 Bad Request

Returned when the access token has no user behind it. client_credentials tokens act as the admin who created the application, so this applies only to tokens issued before application creators were recorded.

401 Unauthorized

Returned when the access token is missing, unknown, revoked, or expired, or when an X-API-Key was sent instead of a bearer token. See OAuth error responses.

403 Forbidden

Returned when the token does not carry the required scope.

404 Not Found

Returned when no document with that ID exists in your organization.

429 Too Many Requests

Returned when your organization exceeds its per-minute request limit.

500 Internal Server Error

Returned when the request fails due to a server error.

Notes

This endpoint is scoped to the organization, not to the access token’s user. Any document ID in your organization resolves, regardless of which document types that user may reach. A user must still be behind the token, so that per-document enforcement can be added later without breaking callers.
The include_* flags only add or remove sections from the response; they never change the document that is returned. With the default body ({}), summary is null and mapped_fields is [] - only the extracted fields are populated. Set include_summary and include_attributes to true to include those sections.
This endpoint returns the same document object as each entry in the Search Documents response. Use Search to find documents by field or attribute, then fetch a single document’s full data here by document_id.

Use Cases

  • Contract review - Retrieve all extracted fields and metadata for a contract
  • Data synchronization - Pull contract data into external systems (CRM, ERP)
  • Reporting - Build dashboards from extracted contract fields
  • Compliance checks - Verify key contract terms like renewal dates and values
  • Workflow integration - Access document data as part of automated workflows