Update User

curl https://api.thanxsandbox.com/users/:id \
  -X PATCH \
  -H "Content-Type: application/json" \
  -H "Accept-Version: v4.0" \
  -H "Accept: application/json" \
  -H "Authorization: Bearer ${token}" \
  -H "X-ClientId: ${client_id}" \
  -d '{
    "user": {
      "email": "<email>",
      "first_name": "<first_name>",
      "last_name": "<last_name>"
    }
  }'

{
  "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"
  }
}

PATCH

users

:id

curl https://api.thanxsandbox.com/users/:id \
  -X PATCH \
  -H "Content-Type: application/json" \
  -H "Accept-Version: v4.0" \
  -H "Accept: application/json" \
  -H "Authorization: Bearer ${token}" \
  -H "X-ClientId: ${client_id}" \
  -d '{
    "user": {
      "email": "<email>",
      "first_name": "<first_name>",
      "last_name": "<last_name>"
    }
  }'

{
  "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"
  }
}

The user’s phone number is not gathered by Thanx with the permission to use it for marketing.

Please review proper request headers here.

curl https://api.thanxsandbox.com/users/:id \
  -X PATCH \
  -H "Content-Type: application/json" \
  -H "Accept-Version: v4.0" \
  -H "Accept: application/json" \
  -H "Authorization: Bearer ${token}" \
  -H "X-ClientId: ${client_id}" \
  -d '{
    "user": {
      "email": "<email>",
      "first_name": "<first_name>",
      "last_name": "<last_name>"
    }
  }'

Parameters

string

required

The user’s id

Body

string

required

The user’s email

string

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.

string

required

The user’s first name

string

required

The user’s last name

hash

The user’s birthday information

Show birth_date

integer

deprecated

The user’s birth year

integer

The user’s birth month

integer

The user’s birth day

string

The user’s zip code

Response

string

The user's identifier

string

The user's email

string

The user's phone number, in E.164 format (eg. +14157582345)

string

The user's first name

string

The user's last name

hash

The user's birthday information

Show birth_date

integer

deprecated

The user's birth year

integer

The user's birth month

integer

The user's birth day

string

The user's zip code

{
  "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"
  }
}

Get User Delete User

⌘I

Consumer API

Reference

Parameters

Body

Response

​Parameters

​Body

​Response

Parameters

Body

Response