1. Fetch the profile
200 OK:
404, not a 403 - membership is what makes them
visible to you. The profile is the redacted partner view: you get the
derived age_band, never the raw dob.
2. Update profile fields
PATCH takes any subset of the profile fields:
200 OK returns the updated user. Validation matches creation: country
must be an assigned ISO alpha-2 code, dob a real past date.
3. Set typed attributes
Beyond the fixed profile, your org’s enabled attribute registry holds custom typed fields (Tenants and members). Write values by key:200 OK:
single_choice
attribute rejects values outside its configured choice list, an attribute key
your org hasn’t enabled is rejected outright. Every stored value carries
provenance, so an API-written value is always distinguishable from one an
admin, the member, or a bulk import wrote.