> ## Documentation Index > Fetch the complete documentation index at: https://docs.trycherry.ai/llms.txt > Use this file to discover all available pages before exploring further. # Filings linked to an entity > Filing orders attached to a legal entity, newest first — the formation once filed, registered-agent service, annual reports, EIN. Defaults to the tenant's primary entity; pass entity_id for another. Exception code/reason are populated when a filing hit an exception. ## OpenAPI ````yaml /openapi.json get /filings openapi: 3.0.3 info: title: Cherry API version: 1.0.0 description: >- Cherry's public developer API — programmatic access to a business's books as Cherry keeps them: bank transactions with their categorizations, the chart of accounts, the double-entry journal, financial statements, legal entities, the tax-obligation calendar, the fiscal health score, and company incorporations (formation, EIN, and state filings). Authenticate every request with an API key: `Authorization: Bearer ck_live_…`. Keys are created in the Cherry app and are scoped to one business (tenant) — there is no tenant id in any URL. Keys carry a `read` and/or `write` scope; every GET needs `read`, mutations need `write`. Conventions: successful responses wrap the payload in `{ "data": … }`; list endpoints add `{ "meta": { "pagination": { limit, offset, nextOffset } } }` — pass `nextOffset` back as `offset` until it is null. Errors are `{ "error": string, "reason"?: string }` with conventional status codes. Dates are `YYYY-MM-DD`; money amounts are numbers in the row's currency. Requests are rate-limited per key with token buckets (429 + `Retry-After` when exhausted); report generation has a smaller budget than plain reads. servers: - url: https://api.trycherry.ai/v1 security: - bearerAuth: [] tags: - name: Transactions description: Bank feed rows and their categorizations. - name: Accounts description: The tenant's chart of accounts. - name: Bank accounts description: >- Connected bank accounts — Plaid-linked and manual. Manual institutions are how developers without a Plaid connection bring their own accounts and transactions. - name: Bank statements description: >- Statement uploads — send a statement PDF/image and Cherry transcribes it, verifies the balances reconcile, and lands the transactions on a manual bank account. The no-export alternative to pushing rows yourself. - name: Journal description: The double-entry journal (entries and lines). - name: Reports description: Trial balance and financial statements. - name: Entities description: Legal entities behind the tenant. - name: Obligations description: The tax/compliance calendar Cherry tracks. - name: Health description: Cherry's composite fiscal readiness score. - name: Incorporations description: >- Company formation, EIN orders, and the state filings that follow — start a formation and track every filing to completion. - name: Meta description: The API's own machine-readable contract. paths: /filings: get: tags: - Incorporations summary: Filings linked to an entity description: >- Filing orders attached to a legal entity, newest first — the formation once filed, registered-agent service, annual reports, EIN. Defaults to the tenant's primary entity; pass entity_id for another. Exception code/reason are populated when a filing hit an exception. operationId: listFilings parameters: - name: entity_id in: query required: false schema: type: string format: uuid description: Entity UUID from GET /entities. Defaults to the primary entity. responses: '200': description: Filings, newest first content: application/json: schema: type: object properties: data: type: array items: $ref: '#/components/schemas/Filing' example: data: - orderId: ord_a1b2c3d4e5f6a7b8 orderType: formation entityId: 3f9c1e0a-8b2d-4e6f-9a01-5c7d2b8e4f10 filingState: DE filingStatus: filed subscriptionStatus: null filingDate: '2026-08-24' exceptionCode: null exceptionReason: null exceptionMessage: null createdAt: '2026-08-19T18:04:11.000Z' updatedAt: '2026-08-24T09:12:45.000Z' '400': description: Error content: application/json: schema: $ref: '#/components/schemas/Error' '401': description: Error content: application/json: schema: $ref: '#/components/schemas/Error' '403': description: Error content: application/json: schema: $ref: '#/components/schemas/Error' '429': description: Error content: application/json: schema: $ref: '#/components/schemas/Error' components: schemas: Filing: type: object description: >- One filing order linked to a legal entity — the formation itself once filed, registered-agent service, annual reports, EIN. Exception fields are populated only when filingStatus is 'exception'. properties: orderId: type: string orderType: type: string entityId: type: string format: uuid nullable: true filingState: type: string nullable: true filingStatus: type: string enum: - submitted - pending - filed - exception - cancelled subscriptionStatus: type: string nullable: true enum: - active - canceled - past_due - null description: For recurring services (registered agent, annual report). filingDate: type: string format: date nullable: true exceptionCode: type: string nullable: true exceptionReason: type: string nullable: true exceptionMessage: type: string nullable: true createdAt: type: string format: date-time updatedAt: type: string format: date-time Error: type: object required: - error properties: error: type: string description: Stable machine-readable error code. reason: type: string description: Human-readable explanation. securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: ck_live_… description: >- Cherry API key, created in the app. Sent as `Authorization: Bearer ck_live_…`. ````