Skip to main content
POST
Enrich document

Authorizations

X-API-KEY
string
header
required

Your API key. Include it in every request as the X-API-KEY header. Create and manage keys in the Developer Platform.

Body

application/json
file_name
string
required

Name of the file being uploaded (e.g. research_report.pdf).

Example:

"research_report.pdf"

published_ts
string<date-time>

Optional publication date/time for the document (ISO 8601). This date will be used as the reference timestamp for search and retrieval.

Example:

"2025-06-15T10:30:00Z"

tags
string[]

Optional list of tag names to apply to the document. Tags can be used to search and filter documents in the Search and Research-Agent services.

Example:
share_with_org
boolean

If true, all members of your organization can access the file once it is processed. If false, only you can access the processed content.

Example:

true

enrichments
enum<string>[]

Optional list of enrichments to apply while processing the document. Each value configures the processing pipeline to run an additional step on the content.

Supported enrichments:

  • reporting_entities: Identifies the document's reporting company, using the same concept as the ReportingEntity reporting detail in Search. This keeps the reporting entity consistent with the rest of the Bigdata corpus, so you can reliably filter private content, transcripts and filings together.
  • translation (coming soon): Translates the document content.
Available options:
reporting_entities,
translation
Example:

Response

Pre-signed URL and document id. PUT the file to the URL to complete the upload; use the id with Get document to poll for status.

url
string<uri>
required

Single-use pre-signed URL. Send a PUT request to this URL with the document file as the body.

id
string
required

Document content ID (32-character uppercase hexadecimal). Use this with Get document to check processing status and perform operations on the document.