Update Fulfillment Routing
PUT/api/shippit/instances/:integration_instance/fulfillment-routing
Saves which Direct warehouses send their fulfillments to this Shippit instance and which are sent automatically.
This endpoint currently requires session authentication; Personal Access Token scope support is in progress.
enabledWarehousesIds(required, array of integers, may be empty) — each listed warehouse's shipping provider becomes this Shippit instance; a warehouse previously routed here and not listed returns to manual fulfillment.automatedWarehousesIds(required, array of integers, may be empty) — the enabled warehouses whose orders dispatch automatically (turns the warehouse's auto dispatch on; enabled-but-not-listed warehouses get it turned off). Ids not also enabled are ignored.
Returns 422 when a warehouse is not a Direct warehouse or another integration already automates it. The response is the same shape as Get Fulfillment Routing.
Authentication: requires a 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 Content
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.