Apply Network Recommendations
POST/api/send-plans/:sendPlan/lines/apply-network-recommendations
Set send lines to the network's own recommendation (today: Amazon's Restock report quantity on FBA lines), in one step. Each changed line is recorded as an edit with the reason network_recommendation, the same as editing it by hand, and the plan totals are recalculated once.
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 (all optional):
- line_ids (integer[], max 5000): only these lines. Omit to use every line in the plan that has a recommendation.
- network (string, max 50): only lines of this network (e.g. amazon_fba).
Lines without a recommendation are never changed. Lines already drafted, or waiting in a draft that is being created, are skipped. The plan must be ready.
Response: applied (lines changed), unchanged (already at the recommended quantity) and skipped (could not be changed any more).
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.
Validation failed — the body is a field → messages map (Laravel shape) or the platform envelope with a stable machine-readable code. Fix the payload and resubmit.
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.