/api/v1/external/companies/{companyId}/entities/Organization. Like all FMV1 entities, the set of available fields is configured per company.
Key Concepts:
- The request body for create and update is a flat JSON object where keys are field
referenceIds (e.g.,name,email). - Responses use the generic entity envelope — all field values live inside a
fieldModelV1Dataobject, alongsideid,createdAt/createdBy,updatedAt/updatedBy, and resolvedcreatedByName/updatedByName. - Updates use merge semantics — provided fields are merged onto the existing data, a key set to
nullclears that field, and omitted fields are left unchanged.PUTis accepted as an alias forPATCH. - Organization uses the
company.fmv1_custom_object:*permission family for all operations.
Field Discovery
Discover the available Organization fields, their types, and which are required via the unified entity configuration endpoint:GET /api/v1/external/companies/{companyId}/entities/organization/configuration.
API Endpoints
The Organization endpoints are listed in the left navigation: create and list (POST / GET on /entities/Organization), and get, update (PATCH, PUT alias), and delete (GET / PATCH / DELETE on /entities/Organization/{entityId}).
Permissions
| Operation | Required Permission |
|---|---|
| Create Organization | company.fmv1_custom_object:create |
| List Organizations | company.fmv1_custom_object:read |
| Get Organization | company.fmv1_custom_object:read |
| Update Organization | company.fmv1_custom_object:update |
| Delete Organization | company.fmv1_custom_object:delete |
