Regenerate Sales Invoice 810
POST/api/sales-invoices/:salesInvoice/edi/regenerate
Rebuild the EDI 810 of an issued sales invoice from the invoice, keeping the same document and control number. Allowed only while the 810 has not been sent (draft or ready) or after it failed or was rejected; a failed or rejected 810 is sent again after rebuilding.
orders:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Authentication: Requires Bearer token and the sales_invoices.send permission.
Errors: 422 when the 810 was already sent — void the invoice before the retailer accepts it, or issue a credit note.
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.