Describe Filing

post/extensions/roboledger/{graph_id}/operations/describe-filing

How one filing is laid out: entity, periods, statements and disclosures by role, axes, and its text — the Items of a 10-K or 10-Q and its largest text blocks, each with the character offset read-text pages from. On the SEC shared repository the filing is read from its public folder — its own document, from any processed year — and a ticker picks it: the latest annual report, narrowed by fiscal_year / period_type, or one accession, or with form: 8-K the latest earnings release and its exhibits. SEC only: a ledger files no document, and its sections read through disclosures and information-block.

Idempotency: supply an Idempotency-Key header to make safe retries; replays within 24 hours return the same envelope. Reusing the key with a different body returns HTTP 409 Conflict.

Authentication

Authenticate in any one of these ways — not all of them:

API key in the X-API-Key header.
Bearer token in the Authorization header.

Path parameters

Name	Type	Description
`graph_id`required	string	Graph Id

Header parameters

Name	Type	Description
`Idempotency-Key`optional	string	Idempotency-Key

Request body

Required, application/json.

Field	Type	Description
`ticker`optional	string	Company ticker. On shared-repository graphs (SEC) it resolves the latest matching filing when report_id is not given; ignored on tenant graphs.
`report_id`optional	string	Specific report identifier. Required on tenant graphs; on SEC, optional when ticker is given.
`fiscal_year`optional	integer	Narrow auto-resolution to this fiscal year focus
`period_type`optional	string	Which forms auto-resolution considers: annual (10-K / 20-F / 40-F, the default) or quarterly (10-Q as well)
`accession`optional	string	SEC only, with ticker: one filing by accession number — a report, or an 8-K from resolved_report.recent_releases
`form`optional	string	SEC only, with ticker: '8-K' reads the latest earnings release

Example request

curl

curl -X POST "https://api.robosystems.ai/extensions/roboledger/{graph_id}/operations/describe-filing" \
  -H "X-API-Key: $ROBOSYSTEMS_API_KEY" \
  -H "Idempotency-Key: <Idempotency-Key>" \
  -H "Content-Type: application/json" \
  -d '{
  "ticker": "string",
  "report_id": "string",
  "fiscal_year": 0,
  "period_type": "string",
  "accession": "string",
  "form": "string"
}'

Responses

200 Successful Response

Field Type Description

operationrequired

string

Kebab-case operation name

operationIdrequired

string

op_-prefixed ULID for audit and SSE correlation

statusrequired

string

Operation lifecycle state

One of: completed, pending, failed

resultoptional

DescribeFilingResponse

Command-specific result payload

DescribeFilingResponse fields

Field	Type	Description
`graph_id`required	string
`report_id`optional	string
`accession`optional	string
`resolved_report`optional	object
`profile`optional	object
`filing`optional	object
`entity`optional	object
`counts`optional	object
`sections`optional	object

atrequired

string

ISO-8601 UTC timestamp

createdByoptional

string

User ID that initiated the operation

idempotentReplayoptional

boolean

True when this envelope came from the idempotency cache — the underlying command did not execute again. False on fresh executions.

Default: false

Status	Meaning
400	Invalid request
401	Authentication required
403	Access denied
404	Resource not found
409	Idempotency-Key conflict — key reused with different body
422	Validation error
429	Rate limit exceeded
500	Internal server error