Send Sales Invoice 810
POST/api/sales-invoices/:salesInvoice/edi/send
Send the EDI 810 for an issued sales invoice: generates and sends it when it is missing, or sends it again when the last attempt failed or the trading partner rejected it. Sends even when the partner's ship notice has not gone out and even when automatic EDI invoices are off for the connection.
orders:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Authentication: Requires Bearer token and the sales_invoices.send permission.
Response: data.edi = {document_id, control_number, status (sent | queued | waiting_for_asn | failed | not_applicable), sent_at, ack_status (accepted | rejected | null), can_send, can_regenerate}.
Errors: 422 when the invoice is not billed over SPS Commerce EDI, is not issued, or its 810 was already sent or is being sent.
Request
Responses
- 200
- 401
- 403
- 404
- 422
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.
Unprocessable Entity
Response Headers
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.