API endpoints for managing manifests and their associated assets/pallets.
A manifest is a container that groups assets/pallets for tracking purposes.
Allocate zimarker code(s) on demand for the calling organization, each with a printable, inline base64 marker image. Allocation is synchronous, atomic, and exactly-once per organization.
Render a zimarker code's marker image on demand. Public, stateless, and addressable by code at a stable URL — no authentication required.
Initial list of asset (pallet) identifiers to include in the manifest.
Optional custom fields to set on the manifest upon creation.
https://docs.zimark.link/_mock/api/integration/rest/api/v1/manifest
https://api.zimark-staging.link/integration/rest/api/v1/manifest
https://api.zimark.link/integration/rest/api/v1/manifest
curl -i -X POST \
https://docs.zimark.link/_mock/api/integration/rest/api/v1/manifest \
-H 'Content-Type: application/json' \
-H 'X-AUTH-KEY: YOUR_API_KEY_HERE' \
-d '{
"identifier": "string",
"assets": [
"string"
],
"customFields": [
{
"deepLink": "string",
"fieldKey": "string",
"fieldValue": "string"
}
],
"gateExternalId": "string"
}'https://docs.zimark.link/_mock/api/integration/rest/api/v1/manifest/{manifestExternalId}/status/{manifestStatus}
https://api.zimark-staging.link/integration/rest/api/v1/manifest/{manifestExternalId}/status/{manifestStatus}
https://api.zimark.link/integration/rest/api/v1/manifest/{manifestExternalId}/status/{manifestStatus}
curl -i -X POST \
https://docs.zimark.link/_mock/api/integration/rest/api/v1/manifest/MAN-2024-001/status/IN_PROGRESS \
-H 'X-AUTH-KEY: YOUR_API_KEY_HERE'Returns a COMPLETED manifest to the PLANNED status so it can be re-dispatched under the same external ID. The completed version is archived (kept COMPLETED, its ID released) and a new PLANNED manifest is created with the same external ID, pallets and custom fields; pallets marked for retirement are reactivated. Requires the organization's "Allow Manifest Return" setting to be enabled. Rejected with 409 when a pallet of the manifest has meanwhile been added to another active (PLANNED / IN_PROGRESS) manifest, since the return would put that pallet in two active manifests at once; remove it from the other manifest first. Returns the new manifest, whose external ID equals the requested one.
https://docs.zimark.link/_mock/api/integration/rest/api/v1/manifest/{manifestExternalId}/return
https://api.zimark-staging.link/integration/rest/api/v1/manifest/{manifestExternalId}/return
https://api.zimark.link/integration/rest/api/v1/manifest/{manifestExternalId}/return
curl -i -X POST \
https://docs.zimark.link/_mock/api/integration/rest/api/v1/manifest/MAN-2024-001/return \
-H 'X-AUTH-KEY: YOUR_API_KEY_HERE'Manifest returned; body is the new PLANNED manifest
Current status of the manifest.
Planning view: total pallets (assets) currently included in this manifest, regardless of loading state. For Total/Loaded execution counts use totalAssetsCount and loadedAssetsCount.
Total assets attached to this manifest, excluding invalid loadings (WRONGLY_LOADED, UNKNOWN_LOADING).
Successfully loaded assets in this manifest, excluding invalid loadings.
Custom key–value fields attached to the manifest.
Validation errors related to this manifest, if any.
Public URL to the Shipment Summary page for this manifest. Present only when manifest status is COMPLETED. Does not expire.
Server-authoritative deadline when the manifest will auto-complete. Present only while the manifest is in PENDING_COMPLETION; omitted otherwise. Completion may occur later than this time if the system is temporarily holding auto-completion (e.g. gate out of service).