Action Items API

You can use the Action Items API to manage tasks for selling partners. When Amazon identifies an action that a selling partner can take, such as a recommendation, an issue to fix, or a task to complete, it publishes an Action Item for you to present to the selling partner in your application.

For example, the Action Items API and Action Plans API support cross-store expansion within Europe (the EXPAND_CROSS_STORE resolution type). For a seller already selling in one European store, Amazon may identify another European store worth expanding into. If the seller chooses to proceed, Amazon configures cross-border pricing, sets up international shipping or Remote Fulfillment, and copies eligible offers into the target store.

Terminology

Use cases

The following use case examples are available for the Action Item API:

• Dismiss an Action Item: Mark an Action Item as not applicable or not of interest to the selling partner.
• Create an Action Plan to Address an Action Item: List actionable items, preview a plan, get the selling partner's confirmation, create the plan, and poll it to a terminal state.

Considerations

• Eligibility. Amazon evaluates eligibility before surfacing an Action Item. There is no eligibility field for your application to evaluate.
• Cost and benefit estimates. The impacts field may be absent. Do not require cost or benefit estimates when displaying an Action Item.
• Plan inputs. Do not send the inputs field on createActionPlan. Amazon derives the plan inputs from the Action Item. Requests that include inputs return HTTP 400.
• Cancelling a running plan is not supported.
• Snoozing an Action Item is not supported, even though SNOOZABLE and SNOOZED exist as status values.
• There is no push notification on state change. Poll getActionPlan and getActionItem instead.
• The marketplaceIds filter on listActionItems returns items associated with any supplied marketplaceId. For multi-store action items, the associated IDs include all the stores in scope, and any store in scope can be used as a filter. The seller must have the marketplaceIds created in their accounts, otherwise listActionItems will return a 403 error.
• Filtering items by ASIN or SKU is not supported.
• Identifiers are opaque. Store actionItemId, actionPlanTemplateId, resolutionDefinitionId, and actionPlanId values as opaque strings returned from the API. Do not parse, validate, or construct them. Production actionItemId values exceed 120 characters and are not UUIDs.
• Regional endpoints. Call the regional endpoint for the seller. For sellers in Europe, use https://sellingpartnerapi-eu.amazon.com. The host declared in the API model is North America; do not use it for European sellers. An empty list response from the North America or Far East endpoints means no items exist there, not an error.
• Sandbox. The API models include static sandbox definitions, so the standard SP-API sandbox workflow (https://sandbox.sellingpartnerapi-eu.amazon.com) applies. Every operation has a static example for a successful call. The only successful static example for createActionPlan is a preview request (mode=PREVIEW); there is no sandbox example for creating a plan.

Roles for the Action Items API v2026-06-01