Create a Recipient
Adds a new recipient — an authorized party who can retrieve artifacts from this dock. IncludestakeholderClass and identifiers appropriate to the recipient’s persona.
Path Parameters
| Parameter | Type | Description |
|---|---|---|
dockId | string | The dock ID |
Request Body
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Required | Recipient display name |
email | string | Required | Recipient email (stored lowercase) |
stakeholderClass | string | Optional | Persona type: mortgagee, agent, policyholder, auditor |
identifiers | object | Optional | Persona-specific key-value identifiers (see below) |
Persona Identifier Patterns
- Insurance
- Real Estate
- Healthcare
- Financial Services
| Persona | Key Identifiers | Auth Model |
|---|---|---|
mortgagee | lender_id, policy_number | Shared passphrase + mTLS cert |
agent | agency_code, policy_number | WebAuthn challenge |
policyholder | email, phone, date_of_birth, policy_number | SMS OTP |
auditor | badge_id, nda_hash | Badge + NDA validation, time-boxed |
Example: Mortgagee (Pre-populated Identifiers)
Store the lender’s identifiers at registration. The policy engine matches these stored values at access time — no runtime submission needed.- Insurance
- Real Estate
- Healthcare
- Financial Services
Example: Policyholder (Runtime Submission)
Add a policyholder with just name and email. They’ll submitdate_of_birth and policy_number when accessing the portal — the policy engine validates the submitted values against the recipe.
- Insurance
- Real Estate
- Healthcare
- Financial Services
Example: Policyholder (Pre-populated)
Alternatively, pre-populate all identifiers at registration. Thephone is required for SMS OTP delivery, so storing it upfront is recommended even if other identifiers are submitted at runtime.
- Insurance
- Real Estate
- Healthcare
- Financial Services
Example: Auditor
- Insurance
- Real Estate
- Healthcare
- Financial Services
Response
Error Handling
| Status | Condition |
|---|---|
400 | email is not a valid email format |
401 | Missing or invalid API key |
404 | Dock not found |
Email addresses are normalized to lowercase and indexed per dock. A dock cannot have two recipients with the same email address. For auditors, compute the
nda_hash by running sha256sum on the signed NDA PDF before registration.Identifiers are optional. You can create a recipient with just name and email, then let them submit identifiers at access time through the portal or API. The policy’s match.identifiers defines what’s required — identifiers can come from the stored record, runtime submission, or both. See Identifier Resolution for details.