What if I only care about acceptance vs rejection?

Branch on acknowledgement.outcome in document.acknowledgement_received.v1. Pull authorized detail only when the outcome requires investigation.

Acknowledgements

Handle 997 and 999 acknowledgements

Understand 997 functional and 999 implementation acknowledgements — webhook delivery, status lifecycle, and remediation.

Start free trial API reference

Quick answer

How fast do acknowledgements arrive?

Depends on partner mailbox processing. Webhooks fire as soon as SignalEDI parses the inbound ack.

997 vs 999

A 997 confirms syntactic acceptance at the functional group level. A 999 reports richer implementation status — treat them as separate lifecycle checkpoints.

Webhook delivery

Subscribe to document.acknowledgement_received.v1 for asynchronous delivery. The safe event includes acknowledgement kind and outcome; use the tenant-scoped receipt and payload endpoints for authorized detail.

Self-healing engine surfaces repeatable mapping fixes
Never reuse ISA/GS control numbers after a hard reject

Retry and exception handling

On reject, update partner mappings or payload fields, then resubmit with fresh control numbers. Keep Certification and Production partner credentials, routes, control numbers, and evidence isolated.

FAQ

Common questions