curl https://api.thanxsandbox.com/partner/users/:id?merchant_id=owierywtwt \
-X PATCH \
-H 'X-ClientId: {client_id}' \
-H 'Accept-Version: v4.0' \
-H 'Content-Type: application/json' \
-H 'Authorization: Bearer {access_token}' \
-d '{
"user": {
"email": "john.smith@example.com",
"first_name": "Jane",
"last_name": "Smith"
}
}'
{
"user": {
"id": "wroeiu2304hfwf",
"email": "john.smith@example.com",
"phone": "+14158672345",
"first_name": "Jane",
"last_name": "Smith",
"birth_date": {
"year": 1987,
"month": 8,
"day": 14
},
"zip_code": "12345",
"updated_at": "2025-02-01T19:00:00Z",
"loyalty": {
"tier": "silver",
"points_balance": 120.50,
"user_joined_at": "2023-12-01T19:00:00Z"
},
"communication_settings": {
"marketing_general_email": true
}
}
}
Users
Update User
This endpoint will update one particular user of the specified merchant.
PATCH
/
partner
/
users
/
:id
curl https://api.thanxsandbox.com/partner/users/:id?merchant_id=owierywtwt \
-X PATCH \
-H 'X-ClientId: {client_id}' \
-H 'Accept-Version: v4.0' \
-H 'Content-Type: application/json' \
-H 'Authorization: Bearer {access_token}' \
-d '{
"user": {
"email": "john.smith@example.com",
"first_name": "Jane",
"last_name": "Smith"
}
}'
{
"user": {
"id": "wroeiu2304hfwf",
"email": "john.smith@example.com",
"phone": "+14158672345",
"first_name": "Jane",
"last_name": "Smith",
"birth_date": {
"year": 1987,
"month": 8,
"day": 14
},
"zip_code": "12345",
"updated_at": "2025-02-01T19:00:00Z",
"loyalty": {
"tier": "silver",
"points_balance": 120.50,
"user_joined_at": "2023-12-01T19:00:00Z"
},
"communication_settings": {
"marketing_general_email": true
}
}
}
Scope required:
users.writeThe user’s phone number is not gathered by Thanx with the permission to use it
for marketing.
To update a user’s notification / email settings, use Update User’s
Communication Settings
instead.
communication_settings is read-only on this endpoint.Parameters
Body
The user’s phone number in E.164 format,
with the country code prefix (e.g.
+14157582345). Phones submitted
without the country code prefix are stored as-is — this endpoint does
not normalize them — and will fail later phone-based lookups (such as
Partner Auth Token) that depend on E.164 parsing.Response
curl https://api.thanxsandbox.com/partner/users/:id?merchant_id=owierywtwt \
-X PATCH \
-H 'X-ClientId: {client_id}' \
-H 'Accept-Version: v4.0' \
-H 'Content-Type: application/json' \
-H 'Authorization: Bearer {access_token}' \
-d '{
"user": {
"email": "john.smith@example.com",
"first_name": "Jane",
"last_name": "Smith"
}
}'
{
"user": {
"id": "wroeiu2304hfwf",
"email": "john.smith@example.com",
"phone": "+14158672345",
"first_name": "Jane",
"last_name": "Smith",
"birth_date": {
"year": 1987,
"month": 8,
"day": 14
},
"zip_code": "12345",
"updated_at": "2025-02-01T19:00:00Z",
"loyalty": {
"tier": "silver",
"points_balance": 120.50,
"user_joined_at": "2023-12-01T19:00:00Z"
},
"communication_settings": {
"marketing_general_email": true
}
}
}