Bulk Create Sales Orders from MCF Orders
POST/api/amazon/unified/fulfillment-orders/bulk-create-sales-orders
Creates and maps a sales order for each order, with the same options and rules as the single-order endpoint: sales_channel_id must be an existing sales channel (null for a manual order), order_status is one of draft, reserved, open, closed, and payment_status is one of unpaid, partially_paid, paid, refunded, partially_refunded (null derives it from the item prices). Orders that already have a sales order are mapped to it and counted in already_existed_ids. Requires both the sales_orders.create and sales_orders.fulfill permissions. Scope is either ids (1–1000 order IDs) or apply_to_all: true with filters (the list filters as a flat map, e.g. {"mapping_status": "unmapped"}), resolved when the job runs and capped at 5,000 orders — a larger set is rejected with 422 stating the matched count. Each order is processed independently; the job's results report succeeded_count, skipped_count, failed_count, has_failures, and per-order failures[]/skipped[] with a reason. Returns tracked_job_log_id.
This endpoint currently requires session authentication; Personal Access Token scope support is in progress.
Request
Responses
- 200
- 401
- 403
- 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.
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.