filings, companies, jurisdictions, and products registered; item operations
also need filing_items. An administrator can configure these in the Records UI.
Find reference values
Find reference IDs through the existingGET /api/v1/mission-controls/{mcId}/records/reference-options?targetKind=system_record&recordType=companies
API; repeat with jurisdictions and products. Follow that endpoint’s pagination.
toiCode and subToiCode use NAIC registry values. A sub-TOI requires its parent TOI.
Discover choices with
GET /api/v1/mission-controls/{mcId}/records/types/filings/fields/toiCode/options?limit=25&query=property
and discover matching sub-TOIs with
GET /api/v1/mission-controls/{mcId}/records/types/filings/fields/subToiCode/options?dependencyValue=01.0&limit=25.
The options endpoint supports query to narrow the results. When changing a TOI,
change or clear an incompatible sub-TOI in the same request. PATCH checks the
resulting filing, including fields you leave unchanged.
Create a filing
Create withPOST /api/v2/managed-filings and Content-Type: application/json:
filing.json, using authorized reference IDs and an MC UUID
or stable slug after mc:. Send it with:
201, includes the created filing and canonical scope, and supplies its detail URL in
Location. API-key creation does not start a Captain session.
Edit a filing
UsePATCH /api/v2/managed-filings/{filingId} to change selected fields: