Create a user
Creates a new user. phone_number is required and must be unique for your brand.
Authorizations
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.
Body
The user's phone number in E.164 format. Required and unique per brand.
20"+15551234567"
50"Jane"
50"Doe"
50"jane.doe@example.com"
Date of birth in MM/DD/YYYY format.
"01/01/1990"
true to opt the user in, false to opt them out, null for no preference.
true
The user's postal code. US ZIP codes only.
"10001"
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.
The channel the user is entering Sotto from.
SHOPIFY, KLAVIYO, HANG, MANYCHAT, FILE "MANYCHAT"
Response
The created user.
The user's unique Sotto ID. Use this for update and delete requests.
1
The user's phone number in E.164 format.
"+15551234567"
UTC time when the user was created.
"2024-01-01T12:00:00Z"
UTC time when the user was last updated.
"2024-10-01T12:00:00Z"
50"Jane"
50"Doe"
50"jane.doe@example.com"
Date of birth in MM/DD/YYYY format.
"01/01/1990"
true if subscribed to messages, false if unsubscribed, null if the user has neither opted in nor opted out.
true
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.
A user's resolved location, derived from their postal code.
Whether the user has been deleted.
false