Bulk Map Shiptheory Delivery Services
POST/api/shiptheory/:integration_instance/delivery-services/bulk-map
Applies one SKU shipping method (or null to clear back to the rules-engine default) to every selected delivery service in a single call.
integrations:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Path parameter:
- integration_instance: the numeric id of the Shiptheory integration instance.
Body fields:
- ids (array of integers, required): the delivery-service row ids to map. At least one required.
- sku_shipping_method_id (integer, required, nullable): the SKU shipping method to apply, or null to clear the selected mappings back to the rules engine. The key must be present (send null to clear); when non-null it must be an existing shipping method.
Returns 200 with { data: { updated } }. Returns 422 with field errors when validation fails.
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 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.