> ## Documentation Index
> Fetch the complete documentation index at: https://docs.canary.effectiveai.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Filing workspace

> Prepare filing records and documents from any HTTP client or agent.

Use the managed-filings APIs for your filing workspace. Use [filing search](/guides/search-filings)
for the regulatory reference catalog. These resources have different IDs.
Pre-review and SERFF staging are not available through this resource yet.

## List filings

[List accessible filings](/guides/managed-filings/read-filings#list-filings).

## Read one filing

[Read filing details](/guides/managed-filings/read-filings#read-one-filing).

## Create and edit a filing

[Choose a scope, create a filing, and edit its details](/guides/managed-filings/create-filings).

## Upload and attach documents

[Upload filing-owned files and manage filing items](/guides/managed-filings/manage-documents).

## Discuss a filing

[Add comments, reply, and resolve discussions](/guides/managed-filings/comments).

## Authenticate

Use an ordinary user-owned Effective API key with MC and filing access. Read-only
keys can read. Resource-scoped, app/system, and record-bot keys are unsupported.
No Captain session or active UI is needed.

Set `EFFECTIVE_API_BASE_URL` to your deployment origin without `/api/v2`, and
provide `EFFECTIVE_API_KEY` through your client's secret environment. Verify the
caller with `GET /api/v2/users/me`.

Use these calls from Codex, another harness, or an application. Store returned
IDs rather than deriving them from tracking numbers or chat state. The filing's
`scope` identifies its Mission Control; v2 calls on an existing filing need only
its ID. To upload documents, pass that `scope` in the
[upload initialization body](/guides/managed-filings/manage-documents#choose-the-upload-location-and-owner).
No MC header is needed.

## Recover from errors

* `401 unauthenticated`: verify the credential and whether its type is supported.
* `403 forbidden`: credential is not permitted for this operation.
* `404 not_found`: filing missing or invisible; these cases are indistinguishable.
* `400 invalid_cursor`: restart the list.
* `400 invalid_request`: correct input; unknown/repeated scalar fields are rejected.
* `409 conflict`: the filing is read-only, a schedule position is occupied, a dependency prevents removal, or inputs changed during validation.
* `503 temporarily_unavailable`: respect `Retry-After` before retrying the read.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.