EPCIS 2.0
GS1 EPCIS 2.0 supply-chain events — export a passport's event history, capture events from partners and ERP systems, and query the event store.
/api/v1/passports/{id}/epcisExport a passport's EPCIS events
Exports one passport's full event history — supply-chain, service, ownership, and captured events — as a single standards-valid GS1 EPCIS 2.0 `EPCISDocument` in JSON-LD. The document carries the GS1 `@context`, `type: "EPCISDocument"`, `schemaVersion: "2.0"`, and an `epcisBody.eventList` of every event TracePass holds for the passport. The passport's Digital Link URI is the EPC on each event, so the export drops straight into any EPCIS-aware repository or auditor toolchain.
/api/v1/epcis/captureCapture EPCIS events
The GS1 EPCIS 2.0 Capture interface. Submit supply-chain events from partners, ERP systems, or shop-floor scanners and TracePass attaches them to the matching passports. The request body accepts four shapes: a full `EPCISDocument`, an `EPCISQueryDocument`, a single bare event, or a bare JSON-LD array of events. Send `Content-Type: application/ld+json`.
/api/v1/epcis/capture/{id}Poll a capture job
Reads the status of an asynchronous EPCIS capture job — the read side of the EPCIS 2.0 capture model. `POST /api/v1/epcis/capture` returns `202 Accepted` with a `captureJobId`; pass that id here to follow the job until it reaches a terminal state.
/api/v1/epcis/eventsQuery EPCIS events
Search your captured supply-chain events using EPCIS 2.0 query parameters. Eight are supported: `EQ_bizStep`, `EQ_disposition`, `EQ_eventType`, `MATCH_epc`, `EQ_bizLocation`, `EQ_readPoint`, `GE_eventTime` and `LT_eventTime`. Values may be `|`-separated to match any of several (`EQ_bizStep=shipping|receiving`). Any other parameter returns `400` rather than being silently ignored, so a typo fails loudly instead of widening your result set.