Hoppa till huvudinnehåll

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 null in API responses, key absent from webhook data when unknown: customerName, customerEmail, customer.name and customer.email of GET /api/v1/orders/{id}, customerName of GET /api/v1/orders and of recentOrders in GET /api/v1/orders/stats/summary can be null, and customer_name and customer_email are left out of the data of the order.created webhook, as every optional field in webhooks is.
  • A search on GET /api/v1/orders matches such an order by its number; the customerId filter finds it too.
  • recentOrders of /stats/summary now carry customerId as well.
  • Added with this change, not breaking: customerType (Consumer or Business in exactly that case, Consumer when left out), and for a Business only customerOrganizationNumber (1 to 30 characters) and customerBuyerReference (1 to 100), returned as customer.type, customer.organizationNumber and customer.buyerReference; and in webhooks customer_type, customer_organization_number, customer_buyer_reference and prices_include_vat on order.created, and vat_rate, vat_amount, line_total_excluding_vat and line_total_including_vat on order.line_added, each left out when null.

Affected operations

  • POST /api/v1/orders
  • GET /api/v1/orders/{id}
  • GET /api/v1/orders
  • GET /api/v1/orders/stats/summary
  • The webhooks order.created and order.line_added

What you do

  • Handle null in responses and a missing key in webhooks, and show customerId instead.

How breaking changes are announced and how long a deprecated endpoint stays: see the versioning policy.