Skip to main content

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.
Base URL:
https://api.prod.commenda.io/api/v1/partner/incorporation
Pass your partner API key in the x-api-key header on every request.
curl --request GET \
  --url 'https://api.prod.commenda.io/api/v1/partner/incorporation/jurisdiction-catalog' \
  --header 'x-api-key: <partner_api_key>'

Object model

Each incorporation is built from a few related records:
Customer
  -> Incorporation
       -> Participants
            -> Commenda OS people/business entities
            -> Participant documents
       -> Intake fields
       -> Status and issues
The 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

  1. Create or find the customer and save customerId.
  2. Choose a jurisdiction and corporation type with the jurisdiction catalog.
  3. Create the incorporation and save incorporation.id.
  4. Create or reuse Commenda OS records for people, business entities, locations, and files.
  5. Register participants and upsert required participant documents.
  6. Submit incorporation-level intake fields and check incorporationValidation.isComplete.
  7. Submit the incorporation for Commenda review, then track status and issues.
For the endpoint-by-endpoint version, including a Singapore private limited company example, see Build an incorporation flow.

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.
NeedCreate or read inLink through
Director or shareholder personCommenda OS PersonsIncorporation Participants
Corporate shareholderCommenda OS Business EntitiesIncorporation Participants
Registered office locationCommenda OS LocationsIntake registeredOfficeAddressLocation
Passport, utility bill, or other source fileCommenda OS FilesParticipant 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.