Recheck Held ASN
POST/api/purchase-orders/:purchase_order/asn/recheck
Re-check a purchase order whose ASN was held back (missing products or an unmapped vendor in the warehouse system) and send it when it is clear. Returns the same response as Send ASN; still-held returns 422 with held_reason and missing_skus, and a PO that isn't held returns 422. The 3PL is not emailed the product-setup sheet again for the same missing SKUs. Returns 422 ASN sending is off for {connection}… when the connection's ASN sending (asn.enabled) was switched off after the PO was sent; receipts keep syncing.
purchase-orders:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Requires permission: purchase_orders.update
Authentication: Requires Bearer token.
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.