Reading this in another language? Use your browser's built-in translate option. Button and field names stay in English on purpose, to match what you see in Keysender.
Customers are the buyer records Keysender keeps for your account: an email, a name, contact details, notes, and the list type that decides whether a buyer is blocked or always allowed. The Customer endpoints keep those records in step with your own CRM or store, so a vetted buyer is treated the same way on every channel.
TL;DR
POST /customer; an email that already exists returns 422 Invalid email, meaning "already there."PUT /customer; email and language cannot change afterward.Make sure you have:
POST /login and the base URL https://panel.keysender.com/api/v1.0.A customer has these fields: id, email, firstName, lastName, language, phone, organizationId, marketingFlag, listType, and notes.
GET /customers. Add page and pagesize for large lists. GET /customer?id=789. POST /customer with at least email and firstName: curl -X POST "https://panel.keysender.com/api/v1.0/customer" \
-H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
-H "Content-Type: application/json" \
-d '{"email": "[email protected]", "firstName": "Alex", "lastName": "Rivera", "notes": "Repeat buyer, verified", "marketingFlag": false}'
lastName, language (default en), phone, notes, marketingFlag, and listType. 422 and the message Invalid email. Read that as "already there" and update the existing record instead. PUT /customer with id and only the fields to change: firstName, lastName, phone, notes, or marketingFlag. The email stays as created. DELETE /customer with {"id": 789}. GET /customer?id=... returns the record you created, and the same buyer appears under Customers in the panel with the notes you wrote. A customer's email is also the payer you send in Creating transactions with the API.
| Symptom | Cause | Action |
|---|---|---|
422 Invalid email on create |
The email exists already, or it is not a valid address | Search for it with GET /customers first |
| A field did not change on update | Only the five editable fields apply; email and language are not |
Confirm the field is one of firstName, lastName, phone, notes, marketingFlag |
| A create was rejected with no matching existing customer | A required field is missing, or email is malformed |
Resend with email and firstName at minimum |
Submit a ticket with the customer id and the request you sent.
That message is also what you get when the email already exists on your account. Search for it with GET /customers first and update the existing record instead of creating a new one.
No. The email is the identity of the record and cannot be changed after creation. Only firstName, lastName, phone, notes, and marketingFlag can be updated.
They are the same records. The listType field is what the panel's block and allow lists set, and it decides how fraud screening treats that buyer on every channel.