EDGE ENGINE Sub-2ms Deterministic V8 Execution • Zero Data Retention Explore API Specs →
Latency: <4ms Edge Availability: 99.99% Standard: GS1 EPCIS 1.2 V8 Pure Compute

EPCIS 1.2 XML Pharmaceutical Supply Chain Event Parser

High-speed EPCIS 1.2 XML parser extracting ObjectEvents, AggregationEvents, BizStep, ReadPoint, and GLN identifiers into JSON.

Official Regulatory Standard & Verification Protocol Authority: U.S. Food & Drug Administration (FDA) DSCSA ↗

Quick Technical Summary: High-speed EPCIS 1.2 XML parser extracting ObjectEvents, AggregationEvents, BizStep, ReadPoint, and GLN identifiers into JSON. Implementation conforms to 21 U.S. Code § 360eee / GS1 EPCIS.

Execution SLA
<4ms Edge (Cloudflare V8)
Governing Norm
GS1 EPCIS 1.2
Throughput Limit
512 KB / Payload
Data Privacy
100% In-Memory (Zero Store)

Specification & Structural Breakdown

EPCIS 1.2 XML is the standard format for exchanging electronic interoperable product tracing data (TI/TH) across the US pharmaceutical supply chain.

Parses ObjectEvent (commissioning, shipping, receiving), AggregationEvent (cases to pallets), and TransformationEvent messages.

XML ElementDescriptionExtracted ValuePurpose
eventTimeEvent TimestampeventTimeISO 8601 UTC timestamp
epcList/epcSerialized EPC URIepcs[]urn:epc:id:sgtin:0030123.045678.123456789012
bizStepBusiness StepbizStepurn:epcglobal:cbv:bizstep:commissioning
readPoint/idRead Point GLNreadPointurn:epc:id:sgln:0030123.00001.0
Interactive Edge Validator

Test EPCIS 1.2 XML Pharmaceutical Supply Chain Event Parser Live

Paste raw inputs up to 32KB and inspect deterministic parsed JSON in real-time across 330+ Cloudflare edge locations. Pure compute, zero cold-starts.

Launch Workbench →

Parsed JSON Response Model

The edge microservice transforms input payloads into strongly-typed hierarchical JSON with zero cold starts:

HTTP 200 JSON Payload
{
  "eventType": "ObjectEvent",
  "eventTime": "2026-08-30T10:30:00Z",
  "action": "OBSERVE",
  "bizStep": "shipping",
  "epcs": [
    "urn:epc:id:sgtin:0030123.045678.123456789012"
  ],
  "readPoint": "urn:epc:id:sgln:0030123.00001.0"
}

Copy-Paste Integration Code

Integrate this validator directly into your application using your production API key:

cURL
curl --request POST \
  --url "https://fda-dscsa-eu-fmd-drug-serialization-api-21-usc-360eee.stanzaapi.com/api/v1/dscsa/validate-barcode" \
  --header "Content-Type: application/json" \
  --header "x-api-key: YOUR_API_KEY" \
  --data '{
  "rawBarcode": "010030123456789621123456789012\u001d1726083110LOT99881"
}'
Node.js (Fetch)
const response = await fetch("https://fda-dscsa-eu-fmd-drug-serialization-api-21-usc-360eee.stanzaapi.com/api/v1/dscsa/validate-barcode", {
  method: "POST",
  headers: {
    "Content-Type": "application/json",
    "x-api-key": process.env.API_KEY || "YOUR_API_KEY"
  },
  body: JSON.stringify({
  "rawBarcode": "010030123456789621123456789012\u001d1726083110LOT99881"
})
});

const data = await response.json();
console.log(data);
Python (Requests)
import requests
import json

url = "https://fda-dscsa-eu-fmd-drug-serialization-api-21-usc-360eee.stanzaapi.com/api/v1/dscsa/validate-barcode"
headers = {
    "Content-Type": "application/json",
    "x-api-key": "YOUR_API_KEY"
}
payload = {
    "rawBarcode": "010030123456789621123456789012\u001d1726083110LOT99881"
}

response = requests.post(url, json=payload, headers=headers)
print(response.json())
Go
package main

import (
	"bytes"
	"fmt"
	"io"
	"net/http"
	"os"
)

func main() {
	url := "https://fda-dscsa-eu-fmd-drug-serialization-api-21-usc-360eee.stanzaapi.com/api/v1/dscsa/validate-barcode"
	payload := []byte(`{"rawBarcode":"010030123456789621123456789012\u001d1726083110LOT99881"}`)

	req, _ := http.NewRequest("POST", url, bytes.NewBuffer(payload))
	req.Header.Add("Content-Type", "application/json")
	req.Header.Add("x-api-key", os.Getenv("API_KEY"))

	res, err := http.DefaultClient.Do(req)
	if err != nil {
		panic(err)
	}
	defer res.Body.Close()
	body, _ := io.ReadAll(res.Body)
	fmt.Println(string(body))
}

Frequently Asked Questions & Technical Notes

Does this handle pallet parent-child aggregation hierarchies?

Yes, AggregationEvents parse parentID (SSCC) and childEPCs arrays seamlessly.

Related FDA DSCSA & EU FMD Prescription Drug Serialization API Formats

Explore sibling specifications and standards in the same developer cluster: