These are WaaS (wallet) customers — not card customers. If you are issuing crypto cards, your card holders are managed separately via the Card Issuer API. The two systems use different customer records and different endpoints. A customer enabled for cards is created through the card onboarding flow; a customer here is created with a single API call and gets crypto wallets immediately.
Type Definitions
Type Definitions
Create a Customer
POST/customers/create-customer
string
required
Customer’s email address. Used as the unique identifier for the customer.
string
Full name of the customer or business.
string
Customer’s phone number.
object
Arbitrary key-value pairs for storing your own reference data (e.g., your internal customer ID, account tier, etc.).
Response
Get Customers
POST/customers/get-customers
Returns all customers under your platform account.
cURL
Response
Get Customer Transactions
POST/customers/get-customer-transactions
Returns the full transaction history for a specific customer.
string
required
The ID of the customer to retrieve transactions for.
cURL
Response
Customer Wallets
After creating a customer, add wallets using the Assets API with the customer-specific endpoints:Customer Data Model
Customer data is isolated — one customer’s wallets and transactions are never accessible from another customer’s context. Your platform account has visibility across all customers.
Sandbox Testing
Replace
YOUR_SANDBOX_TOKEN with a token obtained by authenticating against https://crypto-sandbox.yativo.com/api/v1/. See Sandbox Overview.
