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

# Read filings

> List accessible filing workspaces and read their details and permissions.

Use a user API key with MC and filing read access. Complete the
[authentication setup](/guides/managed-filings#authenticate) first.
These IDs identify filing workspaces, not entries in the [regulatory catalog](/guides/search-filings).

## List filings

List across all active Mission Controls you can view in your tenant. There is no MC filter:

```bash theme={null}
curl --silent --show-error --fail-with-body --get \
  --header "Authorization: Bearer ${EFFECTIVE_API_KEY}" \
  --data-urlencode 'limit=20' \
  "${EFFECTIVE_API_BASE_URL%/}/api/v2/managed-filings"
```

The response has a `filings` array and nullable `nextCursor`. Summaries include
ID, canonical authorization scope (`mc:<MC UUID>`), display name, filing mode, company/jurisdiction/product IDs, tracking
numbers, description, and timestamps. Missing optional metadata is null.
`filingMode` distinguishes `managed`, read-only `reference`, and unclassified
legacy data (`null`). MC access alone does not grant access to private filings.

Repeat the limit with the returned cursor. Default page size is 50; maximum
is 100. Results are ordered by MC UUID ascending, then creation time descending
and filing ID ascending within each MC. Short/empty pages may have a continuation;
stop only at null. Cursors expire 24 hours after the first page. Changing caller
or page size invalidates them. Each call refreshes current MC and filing access;
revoked scopes are skipped. Restart the list to see newly accessible filings that
sort before your current position. No accessible filings returns an empty list.

## Read one filing

Set `FILING_ID` to a returned ID. No MC parameter is needed:

```bash theme={null}
curl --silent --show-error --fail-with-body \
  --header "Authorization: Bearer ${EFFECTIVE_API_KEY}" \
  "${EFFECTIVE_API_BASE_URL%/}/api/v2/managed-filings/${FILING_ID}"
```

Detail adds additional product references, dates/classification, and current
Records permissions. For a Reader, the permission portion is:

```json theme={null}
{
  "permissions": {
    "read": true,
    "edit": false,
    "manageAccess": false
  }
}
```

These are current permissions, not a list of available v2 write endpoints.
Later operations recheck them. References/unclassified filings never advertise
content editing; existing sharing administration remains separate. Private
grants, custom fields, internal context, and audit actors are not exposed.

## Next steps

[Create or edit a filing](/guides/managed-filings/create-filings),
[manage its documents](/guides/managed-filings/manage-documents), or
[read its comments](/guides/managed-filings/comments).
See [error recovery](/guides/managed-filings#recover-from-errors) for failed requests.


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