Skip to main content
POST
Create customers (bulk)
Creates up to 1000 customers in a single request. Each item follows the CustomerInsert schema. registration_date is optional on each item and defaults to the current time when omitted. For regular customers, id, name, and email are required. Anonymous customers need only id and is_anonymous: true.

Request

Response

Returns 201 with a summary object in data when the batch is accepted.

Authorizations

Authorization
string
header
required

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

Body

application/json

Customers to create.

id
string
required

Your customer unique identifier. Must match the sub claim from the customer's OIDC ID token.

is_anonymous
boolean
default:false

Set to true to create an anonymous customer. When true, name and email are not required.

name
string

The full name of the customer. Required unless is_anonymous is true.

Example:

"John Smith"

email
string<email>

The email of the customer. Required unless is_anonymous is true.

status
enum<string>
default:ACTIVE

The status of the customer

Available options:
ACTIVE,
INACTIVE
gender
enum<string> | null

The gender of the customer

Available options:
MALE,
FEMALE,
OTHER
dob
string<date-time> | null

The date of birth of the customer

document_type
string | null

The document type of the customer

document_number
string | null

The document number of the customer

Maximum string length: 50
country
string | null

The country of the customer

Maximum string length: 100
phone
string | null

The customer's phone number in international format

Example:

"+593 99 123 4567"

registration_date
string<date-time>

The date when the customer was registered. Defaults to the current time when omitted.

devices
object[]

Optional device payloads on registration. Use Storefront PATCH /customers/{id} with a devices array to manage structured push devices after registration.

delivery_addresses
object[]
Maximum array length: 10
billing_profiles
object[]
Maximum array length: 10

The customer's consent preferences

metadata
object

Custom metadata for the customer. Must serialize to 1MB or less.

Response

201 - application/json

Ok

data
object