Upsert Network Product Rule
PUT/api/send-planner/networks/:warehouse/products
Create or update one product's rule on a network destination (one rule per product and destination).
send-plans:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Authentication: Bearer Personal Access Token with the send-plans:write scope. The token's user also needs permission to edit the send planner.
Body fields:
- product_id (integer, required): must exist.
- excluded (boolean): never send this product to the network.
- target_days (integer, 1-365, nullable).
- weight (number, 0.1-10, nullable).
- seed_units (integer, 0-100000, nullable).
- listing_multiplier (integer, 1-1000, nullable): a multi-pack listing — single units per listing unit (a 3-pack = 3).
- storage_type (string, nullable): standard | oversize | apparel | footwear | units — which capacity limit the product counts against.
- case_gtin (string, nullable): the case's ITF-14 / GTIN-14, exactly 14 digits (used for case labels).
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.