Retrieve a customer
Return a single customer belonging to your account.
Authorization
ApiKey API key issued to the partner, sent with the Bearer prefix — for example: Authorization: Bearer su_key_9f2c4d1ab3….
Keys minted on the live instance are prefixed su_key_ and keys minted on sandbox su_test_key_. The two instances keep separate key tables and separate hosts, so a sandbox key sent to the live host — or the reverse — answers Invalid API key. rather than falling back to the other environment.
In: header
Path Parameters
Public ID of the customer (cus_…), as returned in the id field of list or retrieve.
Response Body
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/customers/string/"{ "id": "cus_2a108b4eb", "buyer_phone": "9810000001", "buyer_email": "[email protected]", "full_name": "Ram Bahadur", "address": "Kathmandu, Nepal", "created_at": "2026-07-03T10:15:00Z"}Add a customer POST
Record a customer on your account without opening a subscription. `email` identifies the buyer and is required. `phone`, if sent, must be a Nepali mobile number (10 digits starting with 96, 97 or 98); a +977 country code is accepted and stripped. The name and address are your account's own copy of their details and are not shared with other sellers. An email or phone you already hold corrects that customer and returns 200 instead of 201, which makes this endpoint safe to retry. The `phone` and `email` you send here read back as `buyer_phone` and `buyer_email`.
Update a customer PATCH
Correct your account's copy of a customer's name, email or address. Send only the fields you are changing; `""` clears a field. The phone identifies the buyer and cannot be changed. `email` reads back as `buyer_email`.