Fulfillment Hold Access Update For Node Queries

As of the Admin API version 2025-01, apps using the node or nodes GraphQL queries to fetch fulfillment holds will only be able to fetch those that belong to a fulfillment order that they have access to.

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

If your app has the read_assigned_fulfillment_orders scope, you will be able to access holds on fulfillment orders assigned to locations belonging to your app.

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

If your app has the read_marketplace_fulfillment_orders scope, you will be able to access 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 fetch fulfillment holds using a node or nodes GraphQL query 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 2025-01 API version.

When using a node or nodes query to fetch a holds, if your app does not have sufficient access to access the hold then null will be returned for any holds that you do not have access to.

See the fulfillment hold resource for more information on what scopes are required.

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