curl --silent --show-error --fail-with-body --request POST \
--url 'https://api.edi.stateset.com/v1/edi/outbound/{set}/{partner_id}/check' \
--header "Authorization: Bearer $EDI_API_TOKEN" \
--header 'Content-Type: application/json' \
--data '{
"po_number": "PO-123",
"ack_date": "2026-10-20",
"ack_type": "AC",
"lines": []
}'
Runs the outbound pre-send compliance check against the stored PO(s) and the…
Compliance issues, with passed and would_block
POST
/
v1
/
edi
/
outbound
/
{set}
/
{partner_id}
/
check
curl --silent --show-error --fail-with-body --request POST \
--url 'https://api.edi.stateset.com/v1/edi/outbound/{set}/{partner_id}/check' \
--header "Authorization: Bearer $EDI_API_TOKEN" \
--header 'Content-Type: application/json' \
--data '{
"po_number": "PO-123",
"ack_date": "2026-10-20",
"ack_type": "AC",
"lines": []
}'
Path parameters
string
required
855, 856 or 810
string
required
Partner ID
Request body
Ack855 | Asn856 | Invoice810
string (date)
required
string
BAK02 acknowledgment type: AC accept, AD accept with detail, AK acknowledge no detail, RJ reject.
AckLine[]
required
string,null (date)
string
required
Response
No response body. Compliance issues, withpassed and would_block.
Status codes
| Code | Meaning |
|---|---|
200 | Compliance issues, with passed and would_block |
403 | Not this credential’s partner |
422 | Invalid payload or unsupported set |
Using this contract
Read the source OpenAPI document for declared schemas and alternatives. This page also includes documented corrections from the spec overlays. Example IDs and values are illustrative; replace them with records from your workspace.curl --silent --show-error --fail-with-body --request POST \
--url 'https://api.edi.stateset.com/v1/edi/outbound/{set}/{partner_id}/check' \
--header "Authorization: Bearer $EDI_API_TOKEN" \
--header 'Content-Type: application/json' \
--data '{
"po_number": "PO-123",
"ack_date": "2026-10-20",
"ack_type": "AC",
"lines": []
}'
Last modified on October 20, 2026