Documentation Index
Fetch the complete documentation index at: https://docs.commenda.io/llms.txt
Use this file to discover all available pages before exploring further.
Overview
Use this API to help customers complete an incorporation from intake through Commenda review.If you are implementing the flow for the first time, read Core concepts first, then follow Build an incorporation flow.
x-api-key header on every request.
Object model
Each incorporation is built from a few related records:customerId identifies the customer that owns the work. It is not the legal entity being incorporated. The incorporation.id identifies the incorporation for that customer. Participants, documents, intake, status, and issues all attach to that incorporation.
For the full object map, see Core concepts.
Flow at a glance
- Create or find the customer and save
customerId. - Choose a jurisdiction and corporation type with the jurisdiction catalog.
- Create the incorporation and save
incorporation.id. - Create or reuse Commenda OS records for people, business entities, locations, and files.
- Register participants and upsert required participant documents.
- Submit incorporation-level intake fields and check
incorporationValidation.isComplete. - Submit the incorporation for Commenda review, then track status and issues.
Commenda OS resources
Reusable customer records live in the Commenda OS Partner API: people, business entities, locations, and files. The Incorporation API links those records to a specific incorporation when they are needed for roles, addresses, or documents.| Need | Create or read in | Link through |
|---|---|---|
| Director or shareholder person | Commenda OS Persons | Incorporation Participants |
| Corporate shareholder | Commenda OS Business Entities | Incorporation Participants |
| Registered office location | Commenda OS Locations | Intake registeredOfficeAddressLocation |
| Passport, utility bill, or other source file | Commenda OS Files | Participant document upsert |
Incorporation requirements
Fetch requirements after the user chooses a jurisdiction and corporation type. The requirements response describes the current checklist and field contract for that incorporation type. Use it to render your own UI, but treat server validation as authoritative. Participant and document requirements are satisfied by registering participants and upserting participant documents. Incorporation-level fields, such as company name options and registered office address choice, are submitted through the intake endpoint.Status and issues
incorporationValidation.isComplete means the current data is eligible to submit. It does not submit the incorporation by itself.
After submit, use GET /partner/incorporation/{incorporationId}/status for customer-facing progress. Commenda may create partner-visible issues when an incorporation needs correction or additional information. Issues are read-only over the Partner API; fix the underlying data through intake, participants, or documents, and Commenda resolves the issue after review.