Skip to main content
POST
Update a user

Authorizations

x-bigco-hmac-sha256
string
header
required

Base64-encoded HMAC-SHA256 signature of the request. Every request must also include the x-bigco-hmac-username and x-date headers, and POST/PUT requests must include x-digest. See the Authentication guide for the full signing procedure.

Path Parameters

user_id
integer
required

The Sotto ID of the user to update.

Required range: x >= 1
Example:

1

Body

application/json

All fields are optional. Only the fields you supply are updated.

first_name
string | null
Maximum string length: 50
Example:

"Jane"

last_name
string | null
Maximum string length: 50
Example:

"Doe"

email_address
string<email> | null
Maximum string length: 50
Example:

"jane.doe@example.com"

date_of_birth
string | null

Date of birth in MM/DD/YYYY format.

Example:

"01/01/1990"

Example:

true

postal_code
string | null
Example:

"10001"

custom_data
object | null

Key/value pairs of custom data. Each key must match a configured custom data field name, lowercased and snake-cased (e.g. "Loyalty Tier" becomes loyalty_tier). Values may be a string, number, or array.

Example:

Response

The updated user.

id
integer
required

The user's unique Sotto ID. Use this for update and delete requests.

Example:

1

phone_number
string
required

The user's phone number in E.164 format.

Example:

"+15551234567"

date_created
string<date-time>
required

UTC time when the user was created.

Example:

"2024-01-01T12:00:00Z"

date_last_updated
string<date-time>
required

UTC time when the user was last updated.

Example:

"2024-10-01T12:00:00Z"

first_name
string | null
Maximum string length: 50
Example:

"Jane"

last_name
string | null
Maximum string length: 50
Example:

"Doe"

email_address
string<email> | null
Maximum string length: 50
Example:

"jane.doe@example.com"

date_of_birth
string | null

Date of birth in MM/DD/YYYY format.

Example:

"01/01/1990"

true if subscribed to messages, false if unsubscribed, null if the user has neither opted in nor opted out.

Example:

true

custom_data
object | null

Key/value pairs of custom data. Each key must match a configured custom data field name, lowercased and snake-cased (e.g. "Loyalty Tier" becomes loyalty_tier). Values may be a string, number, or array.

Example:
location
object | null

A user's resolved location, derived from their postal code.

is_deleted
boolean
default:false

Whether the user has been deleted.

Example:

false