Customer name and email are optional
2026-11-14 · Breaking change · Upcoming: not yet in production
The customer's name and email are optional: customerName and customerEmail may be left out of
POST /api/v1/orders (an empty string is still a 400; leave the field out instead), and customerId,
a customer number or a pseudonym, is required as before.
What changed
- Name and email are explicit
nullin API responses, key absent from webhookdatawhen unknown:customerName,customerEmail,customer.nameandcustomer.emailofGET /api/v1/orders/{id},customerNameofGET /api/v1/ordersand ofrecentOrdersinGET /api/v1/orders/stats/summarycan benull, andcustomer_nameandcustomer_emailare left out of thedataof theorder.createdwebhook, as every optional field in webhooks is. - A search on
GET /api/v1/ordersmatches such an order by its number; thecustomerIdfilter finds it too. recentOrdersof/stats/summarynow carrycustomerIdas well.- Added with this change, not breaking:
customerType(ConsumerorBusinessin exactly that case,Consumerwhen left out), and for aBusinessonlycustomerOrganizationNumber(1 to 30 characters) andcustomerBuyerReference(1 to 100), returned ascustomer.type,customer.organizationNumberandcustomer.buyerReference; and in webhookscustomer_type,customer_organization_number,customer_buyer_referenceandprices_include_vatonorder.created, andvat_rate,vat_amount,line_total_excluding_vatandline_total_including_vatonorder.line_added, each left out whennull.
Affected operations
POST /api/v1/ordersGET /api/v1/orders/{id}GET /api/v1/ordersGET /api/v1/orders/stats/summary- The webhooks
order.createdandorder.line_added
What you do
- Handle
nullin responses and a missing key in webhooks, and showcustomerIdinstead.
How breaking changes are announced and how long a deprecated endpoint stays: see the versioning policy.