Skip to main content
Use a user API key with MC and filing read access. Complete the authentication setup first. These IDs identify filing workspaces, not entries in the regulatory catalog.

​
List filings

List across all active Mission Controls you can view in your tenant. There is no MC filter:
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:
Detail adds additional product references, dates/classification, and current Records permissions. For a Reader, the permission portion is:
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, manage its documents, or read its comments. See error recovery for failed requests.