updateAutomationConfiguration

put

https://sellingpartnerapi-na.amazon.com/messaging/2026-04-20/automationConfigurations/{automationId}

Updates an existing automation configuration. This is a full replacement operation using PUT semantics; you must provide the complete desired state, including automationDisplayName, automationStatus, and marketplaceAutomations. The marketplaceAutomations entries you provide replace all of the configuration's existing Amazon store entries; any store that you omit is removed from the configuration. To deactivate a configuration, send its complete current state with automationStatus set to DEACTIVATED.

Path Params

automationId

string

required

The unique identifier of the automation configuration to update.

Query Params

marketplaceIds

array of strings

required

A comma-delimited list of Amazon store identifiers for the request. Required for store-scoped operations and authorization. Your application must have permission to operate in the specified stores before processing the request body.

marketplaceIds*

Body Params

The request body for updating an automation configuration.

The request body for updating an existing automation configuration.

automationDisplayName

string

required

length between 1 and 500

^[\p{L}\p{N}\s_-]+$

An updated display name for the automation configuration. To keep the current name, provide the existing value.

automationStatus

string

enum

required

The current status of the automation configuration. A configuration is ACTIVE as soon as it is created. The auto-response text is validated when you create a configuration or update it with automationStatus set to ACTIVE. A request that contains text that is not permitted is rejected with a 422 error. Set the status to DEACTIVATED to stop the configuration from activating without deleting it, and reset it to ACTIVE to resume it.

Show Details

ACTIVE	The automation configuration is active and processing buyer messages.
DEACTIVATED	The automation configuration has been deactivated by the seller.

Allowed:

marketplaceAutomations

array of objects

required

length ≥ 1

The complete list of store-specific automation entries for the configuration. This list replaces all existing entries; any store you omit is removed from the configuration.

marketplaceAutomations*

The store-specific entry within an automation configuration. A seller can have multiple automation configurations, and each configuration can contain entries for one or more Amazon stores. Each store entry defines the automation response content (for example, the auto-response text) and the trigger conditions (for example, specific buyer contact topics or ASINs) for that specific store.

marketplaceId

string

required

The Amazon store identifier.

automationDetails

object

required

The details of the automated action.

triggerConditions

object

required

The conditions that determine when an automation configuration activates for a given store. All conditions must be met simultaneously using AND logic. Within list-based conditions (such as buyerContactTopics or asinList), any single match satisfies that condition using OR logic. For example, if buyerContactTopics contains SHIPPING and WHERES_MY_STUFF, the automation triggers when the buyer's inquiry matches either topic. Trigger conditions cannot overlap with another active automation configuration in the same store; if any combination of ASIN, buyer contact topic, and buyer contact type is already covered by another active configuration, the request is rejected with a 409 error.

Responses

Language

Loading…

Response

Choose an example:

application/json

200The automation configuration was updated successfully.

400Request has missing or invalid parameters and cannot be parsed.

403Indicates that access to the resource is forbidden. Possible reasons include Access Denied, Unauthorized, Expired Token, or Invalid Signature.

404The resource specified does not exist.

409The request conflicts with an existing automation configuration. Possible reasons include a duplicate automationDisplayName or trigger conditions that overlap with another active configuration in the same marketplace.

413The request size exceeded the maximum accepted size.

415The request payload is in an unsupported format.

422The auto-response text contains content that is not permitted.

429The frequency of requests was greater than allowed.

500An unexpected condition occurred that prevented the server from fulfilling the request.

503Temporary overloading or maintenance of the server.