fbaInbound_confirmTransportationOptions
Confirm the chosen transportation option per shipment (write, async).
destructiveAmazon Seller (SP-API)sp.fulfillmentInbound_2024-03-20
Wraps confirmTransportationOptions. Amazon SP-API · confirmTransportationOptions · POST /inbound/fba/2024-03-20/inboundPlans/{inboundPlanId}/transportationOptions/confirmation Gate: commit, choice, fee-bearing — interactive: restate the option and the amount, wait for a typed CONFIRM; autopilot: only within the seller's instruction, named rule (one option, no tie) and stated limits; otherwise ask. The placement option must already be confirmed. IRREVERSIBLE for the plan: once this succeeds, transportation options can no longer be generated or confirmed. The fbaInbound_confirm_plan_options compound does this step for you — use this atomic tool for the Split First flow. An option whose preconditions ask for a confirmed delivery window needs fbaInbound_confirmDeliveryWindowOptions for that shipment first. contactInformation is optional in the model but REQUIRED live for AMAZON_PARTNERED_CARRIER options — Amazon refuses with "ConfirmTransportationOptions does not support confirming PCP options without contact info". name + phoneNumber required when present.
Call it
In an AI client (MCP)
{
"name": "fbaInbound_confirmTransportationOptions",
"arguments": {
"store": "myStore-US",
"plan_id": "<plan_id>",
"transportation_selections": []
}
}From code (Tool API)
curl -X POST https://api.sellersheetai.com/api/v1/tools/fbaInbound_confirmTransportationOptions \
-H "Authorization: Bearer $SELLERSHEET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"store":"myStore-US","plan_id":"<plan_id>","transportation_selections":[]}'Arguments
| Name | Type | Description |
|---|---|---|
storerequired | string | the store ref `<store>-<CC>` (name-country, e.g. 'myStore-US') — one of get_user_context's store_refs, verbatim. |
plan_idrequired | string | the inboundPlanId (from fbaInbound_createInboundPlan or fbaInbound_listInboundPlans). |
transportation_selectionsrequired | object[] | one entry per shipment, shaped as the Body block below — the transportationOptionId the human chose (from fbaInbound_listTransportationOptions) and, for Amazon-partnered options, contactInformation. |
Result
Every tool answers {notification, data, human_action}; data carries:
data.operationId— poll with fbaInbound_getInboundOperationStatus until SUCCESS.data.status— 'IN_PROGRESS'.
Body (Amazon schema): {transportationSelections: [TransportationSelection]} (min 1), each item
contactInformation: {email (max 1024 chars), name* (max 50 chars), phoneNumber* (max 20 chars)}
shipmentId*: string (38–38 chars)
transportationOptionId*: string (38–38 chars)