Add a person to a company with a relationship code

POST 
/v1/parties/:partyId/relationships

Attach an INDIVIDUAL party to a COMPANY party post-onboarding with a relationship code such as DIRECTOR or SECRETARY. Single relationship per call.

The path partyId must resolve to a COMPANY party in the caller's tenant; the body relatedPartyId must resolve to an INDIVIDUAL party in the same tenant. Both misses return 404 PAR004001 (cross-tenant probes collapse into the same code by composite-key lookup).

Required Roles: CLIENT

Requires identity provider authentication with clientId and brandId headers.

Request

Responses

201

Relationship added.

400

Schema validation error (GEN000000). Self-relationship not allowed — partyId equals relatedPartyId (PAR000013). Unsupported relationship type — value accepted by the API schema but not supported by the downstream connector (PAR000010). Missing partyid header (PAR000002). Header / path partyId mismatch (PAR000006).

401

Missing or invalid authentication token (GEN001002) or Role unauthorized (GEN001006) or Tenant context could not be resolved (AUT001001)

403

External application access denied (AUT003001) or Party not in required status (PAR003001)

404

Party not found (PAR004001) or No open binding for the company (CRT004005).

PAR004001 is returned when partyId does not resolve to a COMPANY party in the caller's tenant, when relatedPartyId does not resolve to an INDIVIDUAL party in the caller's tenant, or when either id targets a different tenant.

409

Invalid party type (PAR009004)

500

Internal server error (GEN100000) or Service error (GEN100001)

503

All connector targets are currently unhealthy (CRT103001)