JSON events API
POST CTE events as JSON with KDE validation. Inbound events are validated against FSMA 204 Key Data Elements; failures surface as exceptions before package assembly.
Developer preview for FSMA 204 traceability teams. Scope your ingestion path, validate event payloads, and plan FDA-oriented sortable export workflows with the RegEngine team.
Record a critical tracking event with one signed request. RegEngine issues your API key, workspace ID, and signing secret on request. This call writes a permanent record and can be billed, so use a test workspace and keep the TEST- lot prefix. The Quickstart starts with a read-only call.
export REGENGINE_API_KEY="rge_live_..." # from RegEngine
export REGENGINE_SIGNING_SECRET="..." # from RegEngine
NOW=$(date -u +%Y-%m-%dT%H:%M:%SZ)
TODAY=$(date -u +%Y-%m-%d)
BODY=$(cat <<EOF
{
"source": "<your source system id>",
"events": [
{
"cte_type": "receiving",
"traceability_lot_code": "<the lot code you assigned>",
"product_description": "<product name>",
"quantity": "<number greater than 0>",
"unit_of_measure": "<cases | lbs | kg | pallets | each>",
"location_name": "<your facility name>",
"timestamp": "$NOW",
"kdes": {
"receive_date": "$TODAY",
"receiving_location": "<where the lot arrived>",
"immediate_previous_source": "<who sent it to you>",
"reference_document": "<your ASN or receipt id>",
"tlc_source_reference": "<the lot reference your supplier gave you>"
}
}
]
}
EOF
)
# Sign the exact bytes you send: sha256= plus the HMAC-SHA256 hex digest.
SIGNATURE="sha256=$(printf '%s' "$BODY" | openssl dgst -sha256 -hmac "$REGENGINE_SIGNING_SECRET" -hex | sed 's/^.* //')"
curl -X POST https://regengine.co/api/v1/webhooks/ingest \
-H "X-RegEngine-API-Key: $REGENGINE_API_KEY" \
-H "X-Webhook-Signature: $SIGNATURE" \
-H "Idempotency-Key: $(uuidgen)" \
-H "Content-Type: application/json" \
--data-binary "$BODY"Six core capabilities, one unified API. The building blocks for FSMA 204 traceability workflows, supplier readiness, and FDA response prep.
POST CTE events as JSON with KDE validation. Inbound events are validated against FSMA 204 Key Data Elements; failures surface as exceptions before package assembly.
36 FSMA 204 validation rules (33 stateless + 3 cross-event) evaluate every ingested event. Missing required KDEs, invalid TLCs, and schema violations surface as exceptions in the dashboard.
Fuzzy matching across trading partners with confidence scoring. Deduplicate facilities, carriers, and contacts.
Generate FDA-oriented sortable spreadsheet records and EPCIS 2.0 (Preview) event exports where the enabled workflow and source data support them.
Six-dimension internal readiness signal across export readiness, KDE completeness, CTE coverage, chain integrity, obligation coverage, and FTL product coverage. Not an FDA-issued rating.
10-state machine for FDA response management. Track requests from intake through investigation, response, and closure.
Official client libraries for Python, Node.js, and Go are planned. In the meantime, use our REST API directly. All endpoints accept and return JSON.
Get Notified When SDKs LaunchAPI requests are rate limited. If you hit a limit, the API returns a 429. Stop sending for 60 seconds, then retry.
Need higher throughput? Contact us to discuss your requirements.
Request preview access and we'll scope your first integration path, credentials, and payload contract with you.
Have a RegEngine workspace? Sign in · Read the docs