Create Customer
Creates a new end-customer account under your reseller account.
Customer ID: On success, the response includes a customer_id. Store it — this is the identifier required for all subsequent operations such as POST /api/v1/domains/register and GET /api/v1/domains/orders.
WHOIS contact: The name, address, phone, and email supplied here are automatically set as the registrant, admin, tech, and billing contact for every domain registered under this account. Ensure the details are accurate and in English — non-ASCII characters may cause upstream validation failures.
Email uniqueness: The email address serves as the customer’s login username and must be unique across the platform. Submitting a duplicate email returns a 422 error.
Password requirements: 9–15 characters, including at least one uppercase letter, one lowercase letter, one digit, and one special character from ~ * ! @ $ # % _ + . ? : , { }.
State field: Use the full state or province name (e.g. California, England). If the country has no states, pass Other.
For a list of supported Countries & their States use countries.json
Authorizations
A personal access token. Obtain one from the dashboard under Settings > API Key. Include it in the Authorization header as Bearer <token>. Unauthenticated requests to protected routes return 401 Unauthorized.
Body
Full legal name of the customer (first and last name). Used as the registrant contact name for domain WHOIS records.
1 - 255"John Doe"
International telephone dialling prefix for the customer's country, without the leading '+' (e.g., '1' for US/Canada, '44' for UK, '49' for Germany).
"1"
Customer's phone number, excluding the country dialling code and any leading zeros. Digits only — no spaces, dashes, or parentheses (e.g., '2125551234' for a New York number). Combined with country_code to form a full E.164-compliant number.
"2125551234"
Customer's primary email address. This also serves as the customer's login username for the account. Used for account notifications, password resets, and as the registrant contact email in domain WHOIS records. Must be unique — re-submitting an existing address returns a 422 error.
"john.doe@example.com"
Password for the new account. Use 9–15 characters, including at least one uppercase, one lowercase, one number, and one special character from the allowed set: ~ * ! @ $ # % _ + . ? : , { }
9 - 15"SecureP@ss1"
Two-letter country code as defined by ISO 3166-1 alpha-2 (e.g., 'US' for United States, 'GB' for United Kingdom, 'DE' for Germany). Must be uppercase.
2"US"
Primary street address of the customer (house number and street name). Used as the registrant contact address for domain WHOIS records.
"123 Main Street, Apt 4B"
Full name of the state, province, or region of the customer's address (e.g., 'New York', 'California', 'England'). Use the state names listed in the states array for the relevant country in countries.json. If the customer's country has no states, pass "Other".
"California"
City or locality of the customer's address.
"Los Angeles"
Postal or ZIP code corresponding to the customer's address. Format varies by country (e.g., '10001' for US, 'EC1A 1BB' for UK).
"90001"
Company or organisation name associated with the account. Optional — omit or leave blank for individual (non-business) registrations.
"Acme Corp"