List Send Networks
GET/api/send-planner/networks
List every marketplace fulfillment network the planner can send to (Amazon FBA, Amazon AWD, Walmart WFS, TikTok FBT — whichever integrations you have connected), with the rules that apply to each.
send-plans:readGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Authentication: Bearer Personal Access Token with the send-plans:read scope. The token's user also needs permission to view the send planner.
Response data:
- sources: the source warehouses plans ship from;
serves_localis whether the warehouse ships your own direct / wholesale orders (the protected reserve comes off those first). Set it with Save Send Source Settings. - networks: one entry per marketplace destination with its effective rules (target/floor/max days, weight, lead days and measured lead days, minimum line quantity, seed units for new listings, rounding, blackouts, whether it is a buffer feeding another network via upstream_of), the raw saved rule values in
setting(null when only defaults apply), its sourcelanesin priority order, and its monthlycapacitylimits. Each network also carries buffer_days, floor_strategy, service_level, channel_priority, min_shelf_life_days and inventory_refreshable, andsettingalso holds the saved buffer_days, floor_strategy, service_level, channel_priority, seed_strategy, seed_proxy_pct, seed_proxy_destination_warehouse_id and min_shelf_life_days. - excluded_destinations: network warehouses excluded from planning (id, name, type), so they have no entry in networks.
- capacity_missing: networks with capacity limits for other months but none for this one (destination_warehouse_id, label, month, message) — plans do not cap them this month.
Each network entry also carries inherited_from: the name of the marketplace's own replenishment settings its target_days came from (for example "FBA replenishment settings"), or null when the target is the network default or a value set in the send planner.
Request
Responses
- 200
- 401
- 403
- 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.
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.