Map JSON to X12 (and back)

The translation model

Your application sends JSON that maps through partner-specific profiles to X12. Inbound X12 is normalized back to JSON for webhooks and storage.

• Partner profile = mandatory segments + code lists
• Mappings version with your deploy pipeline

Outbound example

documentTypeCode selects the transaction set; partnerId selects the implementation guide.

curl -X POST https://api.signaledi.com/api/v1/documents/outbound \
  -H "Authorization: Bearer $SIGNALEDI_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "partnerId": "your-partner-id",
  "documentTypeCode": "850",
  "payload": {
    "purchaseOrderNumber": "PO-1042",
    "shipTo": {
      "id": "DC-01",
      "name": "RetailMart DC 01"
    },
    "lines": [
      {
        "lineNumber": 1,
        "sku": "SKU-100",
        "quantity": 24,
        "unitPrice": 12.5
      }
    ]
  }
}'

Partner-specific rules

Retailers differ on ship-to qualifiers, allowance segments, and UOM codes. Configure rules in the partner profile instead of hard-coding segment strings.

Validate before send

Use /tools/edi-validator for ad-hoc samples, then API validation on every outbound POST. Errors reference business fields instead of opaque AK segments.