Submit Fulfillment
POST/api/big-commerce/:integrationInstance/fulfillments/:salesOrderFulfillment/submit
Submit a single fulfillment to BigCommerce, creating the shipment on the BigCommerce order with its tracking details.
This endpoint currently requires session authentication; Personal Access Token scope support is in progress.
Route name: big-commerce.fulfillments.submit-single
Returns 409 with skipped: true when the fulfillment is not eligible to be submitted to this store (already submitted, not fulfilled, a pickup, cancelled, or from another store). Nothing is sent. Every response includes a skipped flag.
Request
Responses
- 200
- 401
- 403
- 404
- 409
- 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.
Conflict
Response Headers
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.