ID of the person
Update a person
Partially updates the specified person’s identity fields. Only the fields present in the request body are applied — omitted fields retain their existing values. The person must be owned by the authenticated customer.
Returns 404 if the person does not exist or is not visible to the authenticated customer (cross-customer access returns 404, not 403).
Path Parameters
Body
application/json
Body
UpdatePersonRequest
Fields to apply to a person. Only non-null fields are applied — omitted or null fields leave the stored value untouched (partial update). firstName and lastName are required.
Example:Grace
Example:Hopper
<= 100 characters
The person’s honorific title.
Allowed values:DRMRMRSMSMISS
Example:MS
The person’s name suffix.
Allowed values:JRSRIIIIIIOBEMBEBSCJPGM
Example:JR
The person’s gender.
Allowed values:MALEFEMALE
Example:FEMALE
National Producer Number. Must start with a non-zero digit and contain only digits.
Match pattern:^[1-9][0-9]*$
<= 12 characters
FINRA CRD number. Must contain only digits.
Match pattern:^[0-9]+$
<= 11 characters
Social Security Number. Must be exactly 9 digits.
Match pattern:^[0-9]*$
>= 9 characters<= 9 characters
Response
application/json
Response
Person updated successfully.
PersonV2
Customer-facing producer identity. SSN is masked — only the last four digits are present via ssnLast4. The full unmasked SSN is available only via GET /v2/persons/{personId}/ssn.
The unique identifier of the person.
Example:550e8400-e29b-41d4-a716-446655440000
The person’s honorific title.
Allowed values:DRMRMRSMSMISS
Example:MS
The person’s first name.
Example:Jane
The name the person prefers to be addressed by, when different from their legal first name.
Example:Janey
The person’s middle name.
Example:Quincy
The person’s last name.
Example:Smith
The person’s name suffix.
Allowed values:JRSRIIIIIIOBEMBEBSCJPGM
Example:JR
The person’s primary contact email address.
Example:jane.smith@example.com
The person’s secondary contact email address.
Example:jane.alt@example.com
The person’s date of birth (YYYY-MM-DD).
Example:1990-05-15
The person’s gender.
Allowed values:MALEFEMALE
Example:FEMALE
The person’s country of citizenship.
Example:US
The person’s state of residence.
Example:CO
Whether the person is a United States citizen.
Example:true
Whether the person is authorized to work in the United States.
Example:true
Whether the person is married.
Example:false
National Producer Number.
Example:12345678
Whether the person’s NPN has been verified against NIPR.
The person’s FINRA Central Registration Depository (CRD) number.
Example:1234567
Last four digits of the Social Security Number. Full SSN available only via GET /v2/persons/{personId}/ssn.
Example:6789
RFC3339 timestamp when the person record was created.
Example:2026-01-15T10:30:00Z
RFC3339 timestamp of the most recent modification.
Example:2026-06-01T14:22:00Z
Authentication
Path Parameters
Body
Retrieve a person's unmasked SSN
Returns the full, unmasked Social Security Number for the specified person. The SSN is masked everywhere else in the API and returned in full only by this endpoint. Every access is recorded in a durable audit log.
Returns 404 if the person does not exist, is not visible to the authenticated customer, or has no SSN on record. A 403 is returned only when the caller’s token lacks the required scope; cross-customer access returns 404, not 403.
Path Parameters
ID of the person
Response
application/json
Response
SSN retrieved successfully.
SsnResponse
Carries a person’s full, unmasked Social Security Number. Returned only by GET /v2/persons/{personId}/ssn; the SSN is masked in all other responses.
The unique identifier of the person.
Example:550e8400-e29b-41d4-a716-446655440000
The full, unmasked Social Security Number (9 digits).
Example:123456789
Authentication
Path Parameters
Associate a person with a firm
Associates an existing person with an existing firm. This is a distinct operation from creating either resource — it only links a person to a firm the caller already owns. Both the person and the firm must be visible to the authenticated customer; if either is unknown or belongs to another customer the response is 404 (never 403), so resource existence is not leaked across customer boundaries.
When role is omitted, it defaults to PRINCIPAL. Re-associating the same person and firm is idempotent and returns 201 with the current association.
Path Parameters
ID of the person
Body
application/json
Body
AssociateFirmRequestV2
Identifies the existing firm to associate with the person, and optionally the person’s role in it.
The unique identifier of the firm to associate.
Example:550e8400-e29b-41d4-a716-446655440000
The person’s role in the firm. Defaults to PRINCIPAL when omitted.
Allowed values:PRINCIPALAGENT_FIRM_MANAGERAGENT
Default:PRINCIPAL
Example:PRINCIPAL
Response
application/json
Response
Association created.
PersonFirmV2
An association between a person and a firm.
The unique identifier of the associated person.
Example:550e8400-e29b-41d4-a716-446655440000
The unique identifier of the associated firm.
Example:660e8400-e29b-41d4-a716-446655440111
The person’s role in the firm.
Allowed values:PRINCIPALAGENT_FIRM_MANAGERAGENT
Example:PRINCIPAL
Authentication
Path Parameters
Body
Addresses
Operations for managing addresses
Delete an address by ID
Deletes a single address by its ID, scoped to the authenticated customer.
Returns 404 if the address does not exist or is not visible to the authenticated customer. A 403 is returned only when the caller’s token lacks the required scope; cross-customer access returns 404, not 403.
Path Parameters
ID of the address
Response
Response
Address deleted successfully.