Skip to main content
PUT
/
stores
/
{storeId}
/
customers
curl --request PUT \
  --url https://api.getredo.com/v2.2/stores/{storeId}/customers \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "email": "jane@example.com",
  "firstName": "Jane",
  "lastName": "Smith",
  "phoneNumber": "+11234567890",
  "location": {
    "street1": "123 Main St",
    "street2": "Suite 12",
    "city": "Seattle",
    "state": "Washington",
    "stateCode": "WA",
    "postalCode": "98101",
    "country": "United States",
    "countryCode": "US",
    "latitude": 47.6062,
    "longitude": -122.3321
  },
  "customFields": {
    "pricing_plan": "com.example.yearly",
    "status": "Active",
    "subscription_source": "web",
    "loyalty_points": 1250,
    "vip_member": true
  }
}
'
{
  "id": "67bd4f1a2e3c8d001a5f9b12",
  "email": "jane@example.com",
  "created": false
}

Documentation Index

Fetch the complete documentation index at: https://developers.redo.com/llms.txt

Use this file to discover all available pages before exploring further.

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

​
storeId
string
required

Store ID

Example:

"64e5a8a1af49a89df37e4ee7"

Body

application/json

Request body for creating or updating a customer profile. The email address is used as the upsert key.

​
email
string<email>
required

Customer email address. Used as the upsert key to find or create the customer.

​
firstName
string

Customer first name

​
lastName
string

Customer last name

​
phoneNumber
string

Customer phone number in E.164 format (e.g., +12345678900). Appended to the existing phone list if not already present.

Example:

"+12345678900"

​
location
Customer Location · object

Customer location information.

​
customFields
object

Custom field values as key-value pairs. Keys are field names and values can be strings, numbers, or booleans. The field type is determined automatically based on the value:

  • String values → STRING custom field
  • Number values → NUMBER custom field
  • Boolean values → BOOLEAN custom field
  • ISO 8601 datetime strings (e.g., "2026-02-24T12:15:00.000Z") → DATE custom field (auto-detected)

If a field name does not already have a declaration, one is created automatically. For STRING fields, unique values are tracked as options (used for segment filtering dropdowns). NUMBER, BOOLEAN, and DATE fields do not track options.

Example:
{
  "subscription_source": "web",
  "status": "Active",
  "loyalty_points": 1250,
  "vip_member": true,
  "signup_date": "2026-02-24T12:15:00.000Z"
}

Response

Existing customer updated

Response after creating or updating a customer profile.

​
id
string
required

Redo customer ID

​
email
string
required

Customer email address

​
created
boolean
required

Whether a new customer was created (true) or an existing customer was updated (false).