Skip to main content

SignalEDI documentation

API-first EDI docs for onboarding, X12 basics, trading partner setup, billing, REST endpoints, and webhooks — with JSON/CSV intake, instant validation, and real-time visibility.

Code Samples

Complete request examples in multiple languages. Click the tabs to switch between cURL, Node.js, Python, and PHP.

Authentication
Include your API key as a Bearer token in the Authorization header.
curl -X GET "https://signaledi.com/api/v1/transactions" \
  -H "Authorization: Bearer sk_live_YOUR_API_KEY" \
  -H "Content-Type: application/json"
Send an Outbound Document
Send an outbound EDI document as JSON to the versioned developer API. Returns 202 with a document id.
curl -X POST "https://signaledi.com/api/v1/documents/outbound" \
  -H "Authorization: Bearer sk_live_YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"partnerId":"your-partner-id","documentTypeCode":"850","payload":{"purchaseOrderNumber":"PO-1001","lines":[{"sku":"SKU-1","quantity":1,"unitPrice":10}]}}'
Get Transaction Status
Retrieve a single transaction by ID.
curl -X GET "https://signaledi.com/api/v1/transactions/txn_abc123" \
  -H "Authorization: Bearer sk_live_YOUR_API_KEY"
Webhook Verification
Verify webhook signatures using HMAC-SHA256.
# SignalEDI signs the string "<X-SignalEDI-Timestamp>.<rawBody>" with HMAC-SHA256.
# The X-SignalEDI-Signature header is "sha256=<hex>". Verify with:
SIGNED="$TIMESTAMP.$BODY"
echo -n "$SIGNED" | openssl dgst -sha256 -hmac "whsec_YOUR_SECRET"

Still have questions?

Our support team typically responds within a few hours during business hours.

Contact support

© 2026 SignalEDI Inc. All rights reserved.