Skip to main content
POST
Creates a new customer with the provided information. The customer can then be used for creating checkouts and other operations. Every Soap API request is authenticated with a bearer token in the Authorization header:
Your API key is in the Soap Dashboard under the Developers section. It looks like key_.... Requests with a missing or invalid API key return 422 — never 401 — with a JSON error field, usually {"error": "API key not found."}. Branch on the status code rather than the message: GET /api/v1/device_pings/latest_geo_check does not yet return the same wording. Never expose your API key in client-side code — it is server-side only.

Authorizations

Authorization
string
header
required

Bearer token authentication using your API key (key_...). Used for every endpoint except POST /api/v1/device_pings.

Body

application/json
email
string
required
Example:

"john@acme.com"

first_name
string
required
Example:

"John"

last_name
string
required
Example:

"Doe"

phone_number
string

Phone number of the customer in ISO 8601 format (10 digits, no hyphens, no country code)

Example:

"8008001234"

date_of_birth
string<date>

Date of birth of the customer in ISO 8601 format (YYYY-MM-DD)

Example:

"1990-01-01"

internal_id
string

Internal ID of the customer in your system.

Example:

"3f1b8c4e-7c2e-4c2c-8d2f-179cf0efb36b"

Response

Customer created.

id
string

Unique identifier for the customer to be used for future transactions.

Example:

"cus_pQsQ4kz3Af6Mb9rCupnWj6VFzxJsmkYK"

internal_id
string
Example:

"3f1b8c4e-7c2e-4c2c-8d2f-179cf0efb36b"

email
string
Example:

"john@acme.com"

first_name
string
Example:

"John"

last_name
string
Example:

"Doe"

phone_number
string
Example:

"8008001234"

date_of_birth
string<date>
Example:

"1990-01-01"

created_at
string<date-time>
Example:

"2025-03-05T18:26:43.069Z"