Update organization

PATCH/v1/organizations/{organizationId}

Update organization metadata. Requires owner or admin role.

How to call this endpoint

Every ACP API request uses bearer authentication. The examples here show the actual request path, auth header, and body shape that the platform expects.

Path, query, and header parameters

These parameters control which ACP object the endpoint acts on and how the request is processed.

Path parameters
NameLocationTypeRequiredDescription
organizationIdpathstringYesOrganization ID
Query parameters
None.

Body schema

Content type: application/json · Required

FieldTypeRequiredDescription
namestringNoHuman-readable name.
slugstringNo
metadataobjectNoFree-form metadata object.

What the API returns

Each response code below includes the documented payload shape for the ACP API.

200Updated organizationapplication/json
FieldTypeRequiredDescription
dataobjectNo
data.idstringNoUnique identifier.
data.namestringNoHuman-readable name.
data.slugstringNo
data.typepersonal | companyNo
data.ownerUserIdstringNo
data.createdByUserIdstringNo
data.statusactive | disabledNoCurrent lifecycle status.
data.metadataobjectNoFree-form metadata object.
data.createdAtstringNoISO 8601 timestamp.
data.updatedAtstringNoISO 8601 timestamp.
data.membershipobjectNo
data.membership.idstringNoUnique identifier.
data.membership.organizationIdstringNo
data.membership.userIdstringNoUser ID.
data.membership.roleowner | admin | billing | developer | member | viewerNo
data.membership.statusactive | removedNoCurrent lifecycle status.
data.membership.invitedByUserIdstringNo
data.membership.joinedAtstringNo
data.membership.createdAtstringNoISO 8601 timestamp.
data.membership.updatedAtstringNoISO 8601 timestamp.
Update organization
Loading...
Response 200
Loading...
See the ACP quickstart and SDK flow