Create Party
Creates a new party — a real-world actor (individual or organization) that can participate in document workflows across multiple docks.Path Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
orgId | string | Required | Organization ID (prefix: org_) |
Request Body
| Parameter | Type | Required | Description |
|---|---|---|---|
type | string | Required | Party type: INDIVIDUAL or ORGANIZATION |
name | string | Required | Full name (individual) or company name (organization) |
email | string | Optional | Primary contact email |
externalRef | string | Optional | External identifier (e.g., EIN:94-1234567, NPI:1234567890) |
metadata | object | Optional | Custom JSON attributes |
Example Request
- Organization Party
- Individual Party
Response
Response Fields
| Field | Type | Description |
|---|---|---|
id | string | Unique party identifier (prefix: pty_) |
organizationId | string | Parent organization ID |
type | string | INDIVIDUAL or ORGANIZATION |
name | string | Party display name |
email | string | Primary contact email |
externalRef | string | External identifier for integrations |
metadata | object | Custom JSON attributes |
createdAt | string | ISO 8601 timestamp |
updatedAt | string | ISO 8601 timestamp |
Error Handling
| Status | Condition |
|---|---|
400 | Invalid party type or missing required fields |
401 | Missing or invalid API key |
404 | Organization not found |
Best Practices
External References: UseexternalRef for authoritative identifiers:
- Organizations: EIN, DUNS, state registration numbers
- Individuals: NPI (healthcare), license numbers, hashed SSN
- Industry classifications
- Geographic regions
- Relationship tiers
- Specializations
Next Steps
After creating a party:- Assign a role in a specific dock
- Create a recipient linked to this party
- Create a machine client associated with this party
Related Concepts
- Parties — Understanding party roles and reuse
- Organizations — Party container
- Recipients — Dock-level access grants linked to parties