Update Contact Info
Update a user’s contact information.
Available to: All authenticated users (own contact information); organization administrators (any user in their organization)
Environments: Live
Rate Limit: No endpoint-specific limit
Update a user’s name, address, and phone number. Pass the target user’s userId; the call writes the contact information you send to that user’s record. If you don’t set a user’s contact information during onboarding, the user is prompted to enter it on their first login.
firstName and lastName fields exceeding a combined 60 characters are rejected, despite each field individually allowing up to 64 characters. The same limit applies to jointFirstName and jointLastName.Two address checks apply to users when all of the following are true: their organization is an evaluation organization, they do not own an unarchived account, and they do not hold an approved trading permission. For these users:
- Restricted countries are rejected. A submission naming a restricted country in either the primary
countryor themailingCountryis rejected, whether or not a separate mailing address is used. This check also runs onupdateContactInfoNameandupdateContactCountry. - U.S. ZIP codes are format-checked. When
countryisUS,postCodemust be a 5-digit ZIP (12345) or ZIP+4 (12345-6789); a missing or malformed value is rejected. The same applies to the mailing ZIP when a separate mailing address is used and its country isUS. The check confirms the format only, not that the ZIP exists or matches the state. This check runs onupdateContactInfoonly.
When a submission fails both checks, the U.S. ZIP code is checked first, so the ZIP error is returned.
HTTP 200 with errorText set, not an error status. Check errorText to confirm the update succeeded.Common Failure Scenarios
- The primary or mailing address names a restricted country, for a user in the group above.
countryisUSandpostCodeis missing or isn’t a valid 5-digit or ZIP+4 code, for a user in the group above.
Error Messages
Authentication
Bearer authentication of the form Bearer <token>, where token is your auth token.
Request
Response
Non-empty if the request failed