POST
/
v1
/
customers

Authorizations

Authorization
string
header
required

Use your Straddle API Key in the Authorization header as Bearer <token> to authorize API requests.

Headers

Straddle-Account-Id
string

For use by platforms to specify an account id and set scope of a request.

Request-Id
string

Optional client generated identifier to trace and debug a request.

Correlation-Id
string

Optional client generated identifier to trace and debug a series of requests.

Body

device
object
required
email
string
required

The customer's email address.

name
string
required

Full name of the individual or business name.

phone
string
required

The customer's phone number in E.164 format. Mobile number is preferred.

type
enum<string>
required
Available options:
individual,
business
address
object | null

An object containing the customer's address. This is optional, but if provided, all required fields must be present.

compliance_profile
object

An object containing the customer's compliance profile. This is optional, but if provided, all required fields must be present for the appropriate customer type.

external_id
string | null

Unique identifier for the customer in your database, used for cross-referencing between Straddle and your systems.

metadata
object | null

Up to 20 additional user-defined key-value pairs. Useful for storing additional information about the customer in a structured format.

Response

201 - text/plain
data
object
required
meta
object
required

Metadata about the API request, including an identifier and timestamp.

response_type
enum<string>
required

Indicates the structure of the returned content.

  • "object" means the data field contains a single JSON object.
  • "array" means the data field contains an array of objects.
  • "error" means the data field contains an error object with details of the issue.
  • "none" means no data is returned.
Available options:
object,
array,
error,
none