Overview
The Business Entity API provides endpoints for managing legal business entities (corporations, LLCs, partnerships, etc.) and their associated data including locations, persons, government identifiers, registrations, documents, and credentials.Core endpoints
Get business entity
Retrieve a single business entity by ID.
Query parameters
Response
The entity is returned as nested groups. The example below is trimmed;
governmentIdentifiers and locations are only present when requested through extends.
Update business entity
Update core business entity information.
Request body
Send only the fields you want to change. Fields the API does not recognize are rejected with
400 Bad Request.
Where the entity’s legal form fixes its fiscal year end, a
fiscalYearDay and fiscalYearMonth that work out to a different year end are rejected with 400 Bad Request.
Response
Returns 200 OK with no body.
List business entities
Get the business entities for a company, one page at a time.
Response
Each entry in
entities has the same shape as Get business entity. Entities are ordered by id; nextCursor is null on the last page.
Business entities the customer has marked as non-controlled (for example, an external parent holding company recorded only to complete the ownership graph) are excluded from this listing unless you pass
includeNonControlled=true. You can also use Get business entity by id to read a non-controlled entity directly, or fetch the company’s organizational structure to see them in context.Get organizational structure
Retrieve the full ownership graph for a company, including non-controlled parent entities. The response is the union of every entity the company owns or that owns into the company, plus the ownership edges between them.
Returns
404 Not Found when the ownership experience is not enabled for the company.
Response
This listing always includes non-controlled entities by design — it powers the org chart visualization.
Key persons
Add key person
Associate a person with a business entity.
Request body
All fields are optional; only the ones you send are changed. Calling the endpoint again for the same person updates their roles on the entity.
When you read a person back through the Commenda OS persons endpoints, the response includes a
governanceRelationships object keyed by role. The set of keys present is a subset of DIRECTOR, AUTHORIZED_SIGNATORY, and BENEFICIAL_OWNER. The BENEFICIAL_OWNER key is set automatically by Commenda’s ownership engine when the person is currently recorded as an ultimate beneficial owner (UBO) of the business entity — it is not assigned through this endpoint.200 OK with no body.
Remove key person
Remove a person from a business entity.
Response
Returns
204 No Content on success.
Assignments
Unassign business entity
Remove the registered agent assigned to a business entity.
Response
Returns
201 Created with no body.
Related resources
- Locations API - Manage business entity addresses
- Government Identifiers API - Manage tax IDs and official numbers
- Registrations API - Manage government registrations
- Documents API - Manage entity documents
- Credentials API - Manage portal access credentials