ID of the person
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
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.
Authentication
Path Parameters
Update an address by ID
Updates 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. Returns 400 when the request body fails validation (V2 error shape).
Path Parameters
ID of the address
Body
application/json
Body
UpdateAddressRequest
Type of address
Allowed values:MAILINGBUSINESSPHYSICAL
First line of the street address.
Example:123 Main St
Second line of the street address (suite, unit, etc.).
Example:Apt 4B
City.
Example:Denver
Two-letter US state code.
Example:CO
ZIP code in 5-digit or ZIP+4 format.
Match pattern:^\d{5}(-\d{4})?$
Example:80202
County name.
Example:Denver
Country code (ISO alpha-2).
Example:US
Date the person moved to this address (YYYY-MM-DD).
Example:2020-01-15
Whether this should be the preferred address. When true, any other preferred address for the same person or firm is automatically unset. Omitting or null is treated as false.
Default:false
Example:false
Response
application/json
Response
Address updated successfully.
AddressV2
Address identifier.
Example:550e8400-e29b-41d4-a716-446655440000
Type of address
Allowed values:MAILINGBUSINESSPHYSICAL
First line of the street address.
Example:123 Main St
Second line of the street address (suite, unit, etc.).
Example:Apt 4B
City.
Example:Denver
Two-letter US state code.
>= 2 characters<= 2 characters
Example:CO
ZIP code in 5-digit or ZIP+4 format.
Match pattern:^\d{5}(-\d{4})?$
Example:80202
County name.
Example:Denver
Country code (ISO alpha-2).
>= 2 characters<= 2 characters
Example:US
Date the person moved to this address (YYYY-MM-DD).
Example:2020-01-15
Whether this is the person’s preferred address.
Example:true
RFC3339 UTC timestamp when the address was created.
Example:2024-01-15T10:30:00Z
RFC3339 UTC timestamp when the address was last updated.
Example:2024-01-15T14:45:00Z
Authentication
Path Parameters
Body
Get an address by ID
Returns 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
application/json
Response
Address retrieved successfully.
AddressV2
Address identifier.
Example:550e8400-e29b-41d4-a716-446655440000
Type of address
Allowed values:MAILINGBUSINESSPHYSICAL
First line of the street address.
Example:123 Main St
Second line of the street address (suite, unit, etc.).
Example:Apt 4B
City.
Example:Denver
Two-letter US state code.
>= 2 characters<= 2 characters
Example:CO
ZIP code in 5-digit or ZIP+4 format.
Match pattern:^\d{5}(-\d{4})?$
Example:80202
County name.
Example:Denver
Country code (ISO alpha-2).
>= 2 characters<= 2 characters
Example:US
Date the person moved to this address (YYYY-MM-DD).
Example:2020-01-15
Whether this is the person’s preferred address.
Example:true
RFC3339 UTC timestamp when the address was created.
Example:2024-01-15T10:30:00Z
RFC3339 UTC timestamp when the address was last updated.
Example:2024-01-15T14:45:00Z