Skip to main content
POST
/
v1
/
customers
Create Customer
curl --request POST \
  --url https://api.daya.co/v1/customers \
  --header 'Content-Type: application/json' \
  --header 'X-Api-Key: <x-api-key>' \
  --data '
{
  "email": "<string>",
  "first_name": "<string>",
  "last_name": "<string>"
}
'
{
  "id": "650e8400-e29b-41d4-a716-446655440000",
  "email": "customer@example.com",
  "first_name": "John",
  "last_name": "Doe",
  "is_verified": false,
  "tier_1_kyc_complete": false,
  "tier_2_kyc_complete": false,
  "capabilities": [],
  "rejection_reasons": [],
  "created_at": "2026-01-05T15:04:05Z",
  "updated_at": "2026-01-05T15:04:05Z"
}

​
Overview

Create a customer record that can be referenced by customer_id in funding account, transfer, and USD virtual account requests. Customers are scoped to the authenticated merchant.

​
Authentication

​
X-Api-Key
string
required
Your merchant API key

​
Request Body

​
email
string
required
Customer email address (must be valid)Example: customer@example.com
Email is normalized to lowercase and trimmed before storage.
​
first_name
string
Customer first name (1–100 characters)Example: John
​
last_name
string
Customer last name (1–100 characters)Example: Doe

​
Request Example

{
  "email": "customer@example.com",
  "first_name": "John",
  "last_name": "Doe"
}

​
Response

​
id
string
required
Unique customer identifier (UUID)
​
email
string
required
Customer email address
​
first_name
string
Customer first name
​
last_name
string
Customer last name
​
is_verified
boolean
Whether the customer has passed verification. false on creation.
​
tier_1_kyc_complete
boolean
Whether tier 1 KYC has been completed. false on creation.
​
tier_2_kyc_complete
boolean
Whether tier 2 KYC has been completed. false on creation.
​
capabilities
array
Customer capabilities and their current status. Empty on creation until verification starts.
​
rejection_reasons
array
Current blocking verification or capability issues. Empty on creation.
​
created_at
string
required
When the customer was created (ISO 8601 timestamp)
​
updated_at
string
required
When the customer was last updated (ISO 8601 timestamp)

​
Success Response

{
  "id": "650e8400-e29b-41d4-a716-446655440000",
  "email": "customer@example.com",
  "first_name": "John",
  "last_name": "Doe",
  "is_verified": false,
  "tier_1_kyc_complete": false,
  "tier_2_kyc_complete": false,
  "capabilities": [],
  "rejection_reasons": [],
  "created_at": "2026-01-05T15:04:05Z",
  "updated_at": "2026-01-05T15:04:05Z"
}

​
Error Responses

{
  "error": {
    "code": "VALIDATION_FAILED",
    "message": "Validation failed",
    "request_id": "550e8400-e29b-41d4-a716-446655440000",
    "validation": "email is required and must be a valid email address"
  }
}

​
Notes

  • Customers are scoped to the authenticated merchant — the same email can exist under different merchants.
  • Once created, a customer can be referenced by customer_id in funding account requests.