Capture 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.

Each event is checked for structural validity (required envelope keys, mandatory event fields, epcList presence), then each EPC in epcList / quantityList is resolved to a passport in your workspace. Valid events are stored and the call returns 202 Accepted with a captureJobId. Processing completes before the response is sent; the 202 status reflects EPCIS 2.0 capture-interface convention. Counts as one v1 write regardless of how many events the document carries.

Volume metered against the plan's maxEpcisEventsPerMonth (1,000 on Basic up to 10,000,000 on Pro, 10 on Free, unlimited on Enterprise). When a single capture call would push the period total over the cap on a paid plan the endpoint returns 402 {"error":"epcis_events_overage_required"} with overageBlocks + totalOverageCents populated — retry the same call with "confirmOverage":true in the body to opt into the per-1,000-event block charge. On Free the same overflow returns 402 {"error":"epcis_events_hard_block"} with an upgrade CTA; no per-block overage path. The call is idempotent two ways — supply an Idempotency-Key header to make the whole request replay-safe, and the platform additionally de-duplicates on each event's EPCIS eventID, so re-sending a document that overlaps a prior capture will not double-store events or double-count against the meter.