Create a contact
POST /v1/contacts
| Field | Type | Required | Notes |
|---|---|---|---|
external_id |
string, max 128 | Yes | Your own ID for this contact. Unique per customer team. |
name |
string, max 300 | See below | Full name of a person, or the company name. |
first_name |
string, max 300 | See below | People only. |
last_name |
string, max 300 | See below | People only. |
email |
email, max 320 | No | |
phone |
string, max 50 | No | |
entity_type |
person or company |
No | Defaults to person. |
Send a name, or at least one non-empty name part. When you send both, the name parts win and WaW builds the full name from them. A company uses name only and cannot have first_name or last_name.
{
"external_id": "person-8421",
"first_name": "Noor",
"last_name": "Janssens",
"email": "noor@example.com",
"phone": "+32470000001"
}Response: 201 Created
{ "id": "7b0c2f4e-1d2a-4c6b-9e8f-3a5d6c7b8e9f", "external_id": "person-8421" }Sending the same request again returns 200 with the same IDs. No duplicate is created.
Update a contact
PATCH /v1/contacts/{id}
Use the WaW id from the create response. You can change name, first_name, last_name, email and phone. Send only the fields you want to change.
{ "phone": "+32470000002" }Response: 200 OK
{ "id": "7b0c2f4e-1d2a-4c6b-9e8f-3a5d6c7b8e9f", "updated": true }- Fields you leave out stay as they are.
nullclearsemailorphone.- A new name also updates the contact’s name on the customer’s bookings.
Good to know
- WaW does not accept an email address that another contact already uses. You get
422. external_idandentity_typecannot change after creation.
