Fulfillment Hold Release Access Update

API

As of the Admin API version 2024-10, apps will not be able to release fulfillment holds unless they have write access to it.

If your app has the write_merchant_managed_fulfillment_orders scope, you will be able to release holds on fulfillment orders assigned to a merchant managed location.

If your app has the write_third_party_fulfillment_orders scope, you will be able to release holds on fulfillment orders assigned to a third party location.

If your app has the write_marketplace_fulfillment_orders scope, you will be able to release holds on fulfillment orders which belong to one of your marketplace's orders.

How will this change effect my app?

This change will only effect apps which release fulfillment holds using the Admin API.

If your app does not currently have sufficient access scopes as defined above then you will need to request the correct access scopes before migrating to the 2024-10 API version.

When using the GraphQL API, if your app does not have sufficient access to release a hold, a user error with the code INVALID_ACCESS will be returned and the hold will not be released.

When using the REST API, if your app does not have sufficient access to release a hold, a 422 error code will be returned and the hold will not be released.

See the fulfillmentOrderReleaseHold mutation for more information on what scopes are required.

See the API access scopes section of the FulfillmentOrder resource for more information about these scopes.