What is implemented (honest scope)
TrackJet ships a GS1 EPCIS 2.0 repository subset: JSON capture and query for the event types and fields that matter for shipment visibility. It is not a full EPCIS certification surface — the implemented subset is documented at /developers/api#epcis, and anything outside it is rejected explicitly rather than half-accepted.
Capture
`` curl -X POST "https://trackjet.world/api/v1/epcis/capture" \ -H "Authorization: Bearer $TRACKJET_API_KEY" \ -H "Content-Type: application/json" \ -d @epcis-document.json ``
Documents are validated against the subset; valid events persist with your key as the owner and an audit-log entry. Capture is idempotent-friendly (resubmitting an identical document does not duplicate events).
Query
`` curl -H "Authorization: Bearer $TRACKJET_API_KEY" \ "https://trackjet.world/api/v1/epcis/events?EPC=urn:epc:id:sscc:0037000.0123456789" ``
Filter by EPC, event time window, and event type. Results return in EPCIS 2.0 JSON shape, scoped to your key — tenants never see each other's events.
Why pair EPCIS with TrackJet
Captured events can correlate with tracked shipments, which means your EPCIS stream inherits the verification story: timelines sealed, anchored in the public transparency log, checkable by your auditors (how).
Onboarding path
- Capture your first document against the sandbox account.
- Map your EPC scheme to shipments (we help — contact).
- Wire your ERP's outbound events to capture; query from your BI.