Skip to Content
CerebrumDocs
GuidesAPI referenceTrust & security

Create a new CRA affiliate or direct child organization

Related workflow: CRA organization set-up · Package access

POST
/v1/organizations/{organizationId}/affiliates

CRA (the default) creates one CRA affiliation. PARENT creates a direct child and its separate servicing-CRA affiliation atomically; the parent must have exactly one active incoming CRA affiliation.

Related: List affiliates · Affiliate package with organization

Authorization

apiKey
headerapikey<token>

Path Parameters

organizationId*string

Primary organization ID

Request Body

application/json
  1. body
type?string

Defaults to CRA. PARENT creates a direct child with the parent's servicing CRA.

Value in"CRA""PARENT"
organization*CreateAffiliateOrganizationPayload

Response Body

The new organization, the relation ID and type, and the primary organization ID.

application/json
  1. response
organization*OrganizationSummaryResponse
relationId*string
type*string
Value in"CRA""PARENT"
primaryOrganizationId*string
Example Request
curl -X POST 'https://api.cerebrum.com/v1/organizations/string/affiliates' \  -H 'apikey: CEREBRUM_API_KEY' \  -H 'Content-Type: application/json' \  -d '{  "type": "PARENT",  "organization": {    "name": "Northwind Staffing West",    "shortName": "northwind-staffing-west"  }}'
Example Response

relationId identifies the relationship, not the child organization. Use organization.id as the child organization ID.

{  "organization": {    "lifecycleStatus": "ACTIVE",    "id": "c8e2b4f6-1a3d-4e5b-9c7a-0f2d4b6e8a19",    "name": "Northwind Staffing West",    "shortName": "northwind-staffing-west",    "delegateWebhooksToCra": false,    "metadata": null,    "createdAt": "2026-11-01T12:00:00.000Z",    "updatedAt": "2026-11-01T12:00:00.000Z"  },  "relationId": "9e3c5a7b-1d4f-4b8e-a2c6-5f7d9b1e3a68",  "type": "PARENT",  "primaryOrganizationId": "a3f1c9d2-6b4e-4c8a-b7e5-2d9f0e1a3c47"}