Submit Fulfillment
POST/api/shipstation/integration-instances/:integration_instance/orders/submit-fulfillment
Manually re-dispatch a SKU.io SalesOrderFulfillment's sales order to ShipStation via the canonical operator-initiated FulfillmentDispatcher. On the defer_dispatch_sof canary this submits the FulfillmentOrder with NO SalesOrderFulfillment at submit (the shipment SOF is minted at ship); it is idempotent — already-submitted FulfillmentOrders are skipped.
Any valid API token can call this endpoint — no specific scope required. Manage tokens.
Body parameters:
sku_fulfillment_id— required integer. A SalesOrderFulfillment id; its sales order is dispatched.
Errors:
- 400 if
sku_fulfillment_idis missing (message:sku_fulfillment_id required) - 404 if the fulfillment (
Fulfillment not found) or its sales order (Sales order not found) does not exist - 502 if the dispatch fails (message:
Failed to submit fulfillment: ...)
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
Response Headers
Validation failed — the body is a field → messages map (Laravel shape) or the platform envelope with a stable machine-readable code. Fix the payload and resubmit.
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.