ERP Orders API

An ERP order record in Zendera ties a transport order back to the originating order in your ERP (internalErpNumber plus the source externalSystem). These read endpoints let your system verify and reconcile that linkage.

Where this fits in your operation

• Reconciliation: confirm that the orders your ERP exported actually exist in Zendera, by paging through or searching the ERP order registry.
• Audit a merge: when several ERP orders were merged into one transport order, the merge log shows which ERP numbers ended up on which internalOrderNumber / freight, and why.

Interactive API Explorer

Authentication

Authorization: apikey YOUR_API_KEY_HERE

Base URLs

• Production: https://app.zenderatms.com/api/
• Staging: https://staging.zenderatms.com/api/

Endpoints

Get one ERP order

GET /v1/erp/{erpOrderId}

Returns the ERPOrder: erpOrderId, internalErpNumber, externalSystem (nullable), organizationId, timestamps.

Search ERP orders

GET /v1/erp/search?q=ERP-2026&page=1&perPage=50

q is the search query; results are page-based (erpOrders[] plus page, perPage, total, totalPages).

Read the merge log

GET /v1/erp/merge/log?page=1&perPage=50

Each entry links the ERP side to the transport side: internalErpNumber, internalOrderNumber, internalFreightNumber, and a reason describing the merge. Same pagination shape as search.

Related documentation

• Orders Import — where ERP orders enter Zendera
• Order Summary — read the resulting transport orders