The market object and the allowed CRUD operations on the related resource endpoint
Markets are automatically enabled at the time of creation, but they can be disabled by sending a
PATCHrequest with the
_disabletrigger attribute set to
true. Similarly, you can use the
_enabletrigger attribute to re-enable a disabled market. Once a market is disabled it is excluded from any authorization scope recalculation: existing access tokens previously created with that market in scope receive a
422 Unprocessable Entityerror on market-specific actions (e.g. if you try to create/update an order or a line item), any attempts to request a new access token with that market in scope receive a
400 Bad Requesterror (due to invalid scope).
Your plan limits refer to active (i.e. enabled) markets only. If you've reached your plan's limit in terms of the number of markets, make sure to disable one of the active markets before enabling a new one.
When setting up a market, you can decide to manage some market-specific features using an external/custom service. Specifically: