Since v3 went live, we've been working through feedback from customers moving over from v2. This release adds a new endpoint for non-payment reasons, raises the rate limit to 60 requests per minute, and adds new fields and filters.
New: non-payment reasons
When a driver delivers an order but doesn't collect payment, they record why, for example INSUFFICIENT_FUNDS or
PRICING_DISCREPANCY. The new Get Many Non-Payment Reasons endpoint
returns those reasons for your orders, newest first.
In v2, an order only included its most recent non-payment reason. A driver may try to collect on the same order more than once, on different days, and v3 returns every attempt. Each result includes the order, the retailer, the delivery date, the reason and when the driver recorded it.
You can filter by order, order number, retailer, reason, delivery date and the date the reason was recorded. For example, to see every reason recorded on an order this month:
curl "https://customer-api.nabis.pro/v3/non-payment-reasons?page=0&limit=100&orderNumber=123456&startCreatedAt=2026-11-01&endCreatedAt=2026-11-30" \
-H 'x-nabis-access-token: <access-token>'
This endpoint replaces v2's lastNonPaymentReason and lastNonPaymentDate fields and filters. The endpoint page lists
every reason value and what it means.
Rate limit raised to 60 requests per minute
The v3 rate limit is now 60 requests per minute for each access token, up from 15. Calls to v2 have their own, separate limit, so they don't count toward your v3 limit.
Every response now includes X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset headers, so you can
slow down before you hit the limit. A 429 response also includes a Retry-After header. The limit is a rolling one:
each request counts toward it for one minute after you make it. See Rate limiting
for details.
Look up an order by order number
Get Many Orders has a new orderNumber filter, so you can look up an order by the
number shown in the Nabis app and on order documents:
curl "https://customer-api.nabis.pro/v3/orders?page=0&limit=10&orderNumber=123456" \
-H 'x-nabis-access-token: <access-token>'
Order manifest links
manifestLink on orders was coming back empty. It now links to the order's shipping
manifest, and is null until a manifest has been generated.
Archived items and batches
Inventory now includes item.isArchived and batch.isArchived, which say whether
the item or the batch itself has been archived. Unlike v2, v3 returns archived items and batches, so use these fields
to tell them apart. Archiving an item also archives its item batches.
We've also clarified item.pricePerUnit: it's the item's standard price, as set on the item. The price charged on an
order can differ, so use the line item's pricePerUnit for what was actually charged.
Who created a credit memo
Credit memos on invoices now include creditMemoCreatedBy, with the id,
firstName, lastName and email of the user who created the credit memo. It's null when no creator is recorded,
for example on some older or system-created credit memos. In v2 this field was just the creator's email address, which
is now creditMemoCreatedBy.email.
Removed: orderInventoryStatus
orderInventoryStatus has been removed from orders.
Getting help
The Migrating from v2 guide has been updated with all of these changes. If you have any questions, reach out to help@nabis.com.