Skip to main content
object

Represents an error in the input of a mutation.

•

The path to the input field that caused the error.

•
String!non-null

The error message.


Was this section helpful?

•
mutation

Charges a shop for features or services one time. This type of charge is recommended for apps that aren't billed on a recurring basis. Test and demo shops aren't charged.

Arguments

•
String!required

The name of the one-time purchase from the app.

•
MoneyInput!required

The amount to be charged to the store for the app one-time purchase.

•
URL!required

The URL where the merchant is redirected after approving the app one-time purchase.

•
BooleanDefault:false

Whether the app one-time purchase is a test transaction.


Fields

•

The newly created app one-time purchase.

•

The URL that the merchant can access to approve or decline the newly created app one-time purchase.

If the merchant declines, then the merchant is redirected to the app and receives a notification message stating that the charge was declined. If the merchant approves and they're successfully invoiced, then the state of the charge changes from pending to active.

You get paid after the charge is activated.

•

The list of errors that occurred from executing the mutation.

•
mutation

Cancels an app subscription on a store.

Arguments

•
ID!required

The ID of the app subscription to be cancelled.

•
BooleanDefault:false

Whether to issue prorated credits for the unused portion of the app subscription. There will be a corresponding deduction (based on revenue share) to your Partner account. For example, if a $10.00 app subscription (with 0% revenue share) is cancelled and prorated half way through the billing cycle, then the merchant will be credited $5.00 and that amount will be deducted from your Partner account.


Fields

•

The cancelled app subscription.

•

The list of errors that occurred from executing the mutation.

•
mutation

Allows an app to charge a store for features or services on a recurring basis.

Arguments

•

Attaches one or more pricing plans to an app subscription. Only one pricing plan can be defined for each available type.

•
String!required

A descriptive name for the app subscription.

•

The replacement behavior when creating an app subscription for a merchant with an already existing app subscription.

•
URL!required

The URL pointing to the page where the merchant is redirected after approving the app subscription.

•
BooleanDefault:false

Whether the app subscription is a test transaction.

•

The number of days of the free trial period, beginning on the day that the merchant approves the app charges.


Fields

•

The newly-created app subscription.

•

The URL pointing to the page where the merchant approves or declines the charges for an app subscription.

•

The list of errors that occurred from executing the mutation.

•
mutation

Updates the capped amount on the usage pricing plan of an app subscription line item.

Arguments

•
MoneyInput!required

The new maximum amount of usage charges that can be incurred within a subscription billing interval.

•
ID!required

The ID of the app subscription line item to be updated.


Fields

•

The updated app subscription.

•

The URL where the merchant approves or declines the updated app subscription line item.

•

The list of errors that occurred from executing the mutation.

•
mutation

Enables an app to charge a store for features or services on a per-use basis. The usage charge value is counted towards the cappedAmount limit that was specified in the appUsagePricingDetails field when the app subscription was created. If you create an app usage charge that causes the total usage charges in a billing interval to exceed the capped amount, then a Total price exceeds balance remaining error is returned.

Arguments

•
String!required

The description of the app usage record.

•

A unique key generated by the client to avoid duplicate charges. Maximum length of 255 characters.

•
MoneyInput!required

The price of the app usage record.

Anchor to subscriptionLineItemIdsubscriptionLineItemId
•
ID!required

The ID of the app subscription line item to create the usage record under. This app subscription line item must have a usage pricing plan.


Fields

•

The newly created app usage record.

•

The list of errors that occurred from executing the mutation.

•
mutation

Starts the cancelation process of a running bulk operation.

There may be a short delay from when a cancelation starts until the operation is actually canceled.

Arguments

•
ID!required

The ID of the bulk operation to cancel.


Fields

•

The bulk operation to be canceled.

•

The list of errors that occurred from executing the mutation.

•
mutation

Creates and runs a bulk operation query.

See the bulk operations guide for more details.

Arguments

•
String!required

The query to be executed in bulk.


Fields

•

The newly created bulk operation.

•

The list of errors that occurred from executing the mutation.

•
mutation

Adds products to a collection.

Arguments

•
ID!required

The ID of the collection that's being updated. This can't be a smart collection.

•
[ID!]!required

The IDs of the products that are being added to the collection. If any of the products is already present in the input collection, then an error is raised and no products are added.


Fields

•

The updated collection. Returns null if an error is raised.

•

The list of errors that occurred from executing the mutation.

•
mutation

Creates a collection.

Arguments

•

The properties to use when creating the collection.


Fields

•

The collection that has been created.

•

The list of errors that occurred from executing the mutation.

•
mutation

Deletes a collection.

Arguments

•

The collection to delete.


Fields

•

The ID of the collection that was deleted. Returns null if the collection doesn't exist.

•
Shop!non-null

The shop associated with the collection.

•

The list of errors that occurred from executing the mutation.

•
mutation

Removes a set of products from a given collection. The mutation can take a long time to run. Instead of returning an updated collection the mutation returns a job, which should be polled. For use with manual collections only.

Arguments

•
ID!required

The ID of the collection to remove products from. The ID must reference an existing manual collection.

•
[ID!]!required

The IDs of products to remove from the collection. The mutation doesn't validate that the products belong to the collection or whether the products exist.


Fields

•

The asynchronous job removing the products.

•

The list of errors that occurred from executing the mutation.

•
mutation

Asynchronously reorders a set of products within a specified collection. Instead of returning an updated collection, this mutation returns a job, which should be polled. The Collection.sortOrder must be MANUAL. Displaced products will have their position altered in a consistent manner, with no gaps.

Arguments

•
ID!required

The ID of the collection on which to reorder products.

•

A list of moves to perform, which will be evaluated in order. Up to 250 moves are supported, the newPosition does not have to be unique.


Fields

•

The asynchronous job reordering the products.

•

The list of errors that occurred from executing the mutation.

•
mutation

Updates a collection.

Arguments

•

The updated properties for the collection.


Fields

•

The updated collection.

•

The asynchronous job updating the products based on the new rule set.

•

The list of errors that occurred from executing the mutation.

•
mutation

Add tax exemptions for the customer.

Arguments

•
ID!required

The ID of the customer to update.

•

The list of tax exemptions to add for the customer, in the format of an array or a comma-separated list. Example values: ["CA_BC_RESELLER_EXEMPTION", "CA_STATUS_CARD_EXEMPTION"], "CA_BC_RESELLER_EXEMPTION, CA_STATUS_CARD_EXEMPTION".


Fields

•

The updated customer.

•

The list of errors that occurred from executing the mutation.

•
mutation

Create a new customer. As of API version 2022-10, apps using protected customer data must meet the protected customer data requirements.

Arguments

•

The input fields to create a customer.


Fields

•

The created customer.

•

The list of errors that occurred from executing the mutation.

•
mutation

Delete a customer. As of API version 2022-10, apps using protected customer data must meet the protected customer data requirements.

Arguments

•

Specifies the customer to delete.


Fields

•

The ID of the deleted customer.

•
Shop!non-null

The shop of the deleted customer.

•

The list of errors that occurred from executing the mutation.

•
mutation

Generate an account activation URL for a customer.

Arguments

•
ID!required

The ID of the customer that the URL is generated for.


Fields

Anchor to accountActivationUrlaccountActivationUrl
•

The generated account activation URL.

•

The list of errors that occurred from executing the mutation.

•
mutation

Creates a credit card payment method for a customer using a session id. These values are only obtained through card imports happening from a PCI compliant environment. Please use customerPaymentMethodRemoteCreate if you are not managing credit cards directly.

Arguments

•

The billing address.

•
ID!required

The ID of the customer.

•
String!required

The Cardserver session ID. Obtained by storing card data with Shopify's Cardsink. Exchanging raw card data for a session ID must be done in a PCI complaint environment.


Fields

Anchor to customerPaymentMethodcustomerPaymentMethod
•

The customer payment method.

•

If the card verification result is processing. When this is true, customer_payment_method will be null.

•

The list of errors that occurred from executing the mutation.

•
mutation

Updates the credit card payment method for a customer.

Arguments

•

The billing address.

•
ID!required

The ID of the customer payment method.

•
String!required

The Cardserver session ID.


Fields

Anchor to customerPaymentMethodcustomerPaymentMethod
•

The customer payment method.

•

If the card verification result is processing. When this is true, customer_payment_method will be null.

•

The list of errors that occurred from executing the mutation.

•
mutation

Revokes a customer's payment method.

Arguments

Anchor to customerPaymentMethodIdcustomerPaymentMethodId
•
ID!required

The ID of the customer payment method to be revoked.


Fields

Anchor to revokedCustomerPaymentMethodIdrevokedCustomerPaymentMethodId
•

The ID of the revoked customer payment method.

•

The list of errors that occurred from executing the mutation.

•
mutation

Sends a link to the customer so they can update a specific payment method.

Arguments

Anchor to customerPaymentMethodIdcustomerPaymentMethodId
•
ID!required

The payment method to be updated.

•

Specifies the payment method update email fields. Only the 'from' and 'bcc' fields are accepted for input.


Fields

•

The customer to whom an update payment method email was sent.

•

The list of errors that occurred from executing the mutation.

•
mutation

Remove tax exemptions from a customer.

Arguments

•
ID!required

The ID of the customer to update.

•

The list of tax exemptions to remove for the customer, in the format of an array or a comma-separated list. Example values: ["CA_BC_RESELLER_EXEMPTION", "A_STATUS_CARD_EXEMPTION"], "CA_BC_RESELLER_EXEMPTION, CA_STATUS_CARD_EXEMPTION".


Fields

•

The updated customer.

•

The list of errors that occurred from executing the mutation.

•
mutation

Replace tax exemptions for a customer.

Arguments

•
ID!required

The ID of the customer to update.

•

The list of tax exemptions that will replace the current exemptions for a customer. Can be an array or a comma-separated list. Example values: ["CA_BC_RESELLER_EXEMPTION", "A_STATUS_CARD_EXEMPTION"], "CA_BC_RESELLER_EXEMPTION, CA_STATUS_CARD_EXEMPTION".


Fields

•

The updated customer.

•

The list of errors that occurred from executing the mutation.

•
mutation

Update a customer's attributes. As of API version 2022-10, apps using protected customer data must meet the protected customer data requirements.

Arguments

•

Provides updated fields for the customer. To set marketing consent, use the customerEmailMarketingConsentUpdate or customerSmsMarketingConsentUpdate mutations instead.


Fields

•

The updated customer.

•

The list of errors that occurred from executing the mutation.

•
mutation

Updates a customer's default address.

Arguments

•
ID!required

The ID of the customer's new default address.

•
ID!required

The ID of the customer whose default address is being updated.


Fields

•

The customer whose address was updated.

•

The list of errors that occurred from executing the mutation.

•
mutation

Create a delivery profile.

Arguments

•

Specifies the input fields for a delivery profile.


Fields

•

The delivery profile that was created.

•

The list of errors that occurred from executing the mutation.

•
mutation

Enqueue the removal of a delivery profile.

Arguments

•
ID!required

The ID of the delivery profile to remove.


Fields

•

The delivery profile deletion job triggered by the mutation.

•

The list of errors that occurred from executing the mutation.

•
mutation

Update a delivery profile.

Arguments

•
ID!required

The ID of the delivery profile to update.

Anchor to leaveLegacyModeProfilesleaveLegacyModeProfiles
•

Whether this delivery profile should leave legacy mode.

•

Specifies the input fields for a delivery profile.


Fields

•

The delivery profile that was updated.

•

The list of errors that occurred from executing the mutation.

•
mutation

Set the delivery settings for a shop.

Arguments

•

Specifies the input fields for the delivery shop level settings.


Fields

•

The updated delivery shop level settings.

•

The list of errors that occurred from executing the mutation.

•
mutation

Assigns a location as the shipping origin while using legacy compatibility mode for multi-location delivery profiles.

Arguments

•
ID!required

The ID of the location to assign as the shipping origin.


Fields

•

The list of errors that occurred from executing the mutation.

•
mutation

Adds tags to multiple draft orders.

Arguments

•

The IDs of the draft orders to add tags to.

•

The ID of the draft order saved search for filtering draft orders on.

•

The conditions for filtering draft orders on. See the detailed search syntax.

•
[String!]!required

List of tags to be added.


Fields

•

The asynchronous job for adding tags to the draft orders.

•

The list of errors that occurred from executing the mutation.

•
mutation

Deletes multiple draft orders.

Arguments

•

The IDs of the draft orders to delete.

•

The ID of the draft order saved search for filtering draft orders on.

•

The conditions for filtering draft orders on. See the detailed search syntax.


Fields

•

The asynchronous job for deleting the draft orders.

•

The list of errors that occurred from executing the mutation.

•
mutation

Removes tags from multiple draft orders.

Arguments

•

The IDs of the draft orders to remove tags from.

•

The ID of the draft order saved search for filtering draft orders on.

•

The conditions for filtering draft orders on. See the detailed search syntax.

•
[String!]!required

List of tags to be removed.


Fields

•

The asynchronous job for removing tags from the draft orders.

•

The list of errors that occurred from executing the mutation.

•
mutation

Calculates the properties of a draft order. Useful for determining information such as total taxes or price without actually creating a draft order.

Arguments

•

The fields for the draft order.


Fields

Anchor to calculatedDraftOrdercalculatedDraftOrder
•

The calculated properties for a draft order.

•

The list of errors that occurred from executing the mutation.

•
mutation

Completes a draft order and creates an order.

Arguments

•
ID!required

The draft order to complete.

•

The gateway for the completed draft order.

•
BooleanDefault:false

Whether the payment is pending.

•

A channel definition handle used for sales channel attribution.


Fields

•

The completed draft order.

•

The list of errors that occurred from executing the mutation.

•
mutation

Creates a draft order.

Arguments

•

The fields used to create the draft order.


Fields

•

The created draft order.

•

The list of errors that occurred from executing the mutation.

•
mutation

Creates a draft order from order.

Arguments

•
ID!required

Specifies the order's id that we create the draft order from.


Fields

•

The created draft order.

•

The list of errors that occurred from executing the mutation.

•
mutation

Deletes a draft order.

Arguments

•

Specify the draft order to delete by its ID.


Fields

•

The ID of the deleted draft order.

•

The list of errors that occurred from executing the mutation.

•
mutation

Duplicates a draft order.

Arguments

•
ID

The ID of the draft order to duplicate.

•

The ID of the draft order to duplicate.


Fields

•

The newly duplicated draft order.

•

The list of errors that occurred from executing the mutation.

•
mutation

Previews a draft order invoice email.

Arguments

•

Specifies the draft order invoice email fields.

•
ID!required

Specifies the draft order invoice email to preview.


Fields

•

The draft order invoice email rendered as HTML to allow previewing.

•

The subject preview for the draft order invoice email.

•

The list of errors that occurred from executing the mutation.

•
mutation

Sends an email invoice for a draft order.

Arguments

•

Specifies the draft order invoice email fields.

•
ID!required

Specifies the draft order to send the invoice for.


Fields

•

The draft order an invoice email is sent for.

•

The list of errors that occurred from executing the mutation.

•
mutation

Updates a draft order.

If a checkout has been started for a draft order, any update to the draft will unlink the checkout. Checkouts are created but not immediately completed when opening the merchant credit card modal in the admin, and when a buyer opens the invoice URL. This is usually fine, but there is an edge case where a checkout is in progress and the draft is updated before the checkout completes. This will not interfere with the checkout and order creation, but if the link from draft to checkout is broken the draft will remain open even after the order is created.

Arguments

•
ID!required

Specifies the draft order to update.

•

The draft order properties to update.


Fields

•

The updated draft order.

•

The list of errors that occurred from executing the mutation.

•
mutation

Creates a new Amazon EventBridge webhook subscription.

Building an app? If you only use app-specific webhooks, you won't need this. App-specific webhook subscriptions specified in your shopify.app.toml may be easier. They are automatically kept up to date by Shopify & require less maintenance. Please read About managing webhook subscriptions.

Arguments

•

The type of event that triggers the webhook.

•

Specifies the input fields for an EventBridge webhook subscription.


Fields

•

The list of errors that occurred from executing the mutation.

•

The webhook subscription that was created.

•
mutation

Updates an Amazon EventBridge webhook subscription.

Building an app? If you only use app-specific webhooks, you won't need this. App-specific webhook subscriptions specified in your shopify.app.toml may be easier. They are automatically kept up to date by Shopify & require less maintenance. Please read About managing webhook subscriptions.

Arguments

•
ID!required

The ID of the webhook subscription to update.

•

Specifies the input fields for an EventBridge webhook subscription.


Fields

•

The list of errors that occurred from executing the mutation.

•

The webhook subscription that was updated.

•
mutation

Triggers any workflows that begin with the trigger specified in the request body. To learn more, refer to Create Shopify Flow triggers.

Arguments

•
String

The payload needed to run the Trigger.

•

The handle of the trigger.

•

The payload needed to run the Trigger.


Fields

•

The list of errors that occurred from executing the mutation.

•
mutation

Cancels a fulfillment.

Arguments

•
ID!required

The ID of the fulfillment to be canceled.


Fields

•

The canceled fulfillment.

•

The list of errors that occurred from executing the mutation.

•
mutation

Creates a fulfillment for one or many fulfillment orders. The fulfillment orders are associated with the same order and are assigned to the same location.

Arguments

•

The input fields used to create a fulfillment from fulfillment orders.

•

An optional message for the fulfillment request.


Fields

•

The created fulfillment.

•

The list of errors that occurred from executing the mutation.

•
mutation

Creates a fulfillment event for a specified fulfillment.

Arguments

•

The input fields used to create a fulfillment event for a fulfillment.


Fields

•

The created fulfillment event.

•

The list of errors that occurred from executing the mutation.

•
mutation

Accept a cancellation request sent to a fulfillment service for a fulfillment order.

Arguments

•
ID!required

The ID of the fulfillment order associated with the cancellation request.

•

An optional reason for accepting the cancellation request.


Fields

•

The fulfillment order whose cancellation request was accepted.

•

The list of errors that occurred from executing the mutation.

•
mutation

Accepts a fulfillment request sent to a fulfillment service for a fulfillment order.

Arguments

•
ID!required

The ID of the fulfillment order associated with the fulfillment request.

•

An optional reason for accepting the fulfillment request.


Fields

•

The fulfillment order whose fulfillment request was accepted.

•

The list of errors that occurred from executing the mutation.

•
mutation

Marks a fulfillment order as canceled.

Arguments

•
ID!required

The ID of the fulfillment order to mark as canceled.


Fields

•

The fulfillment order that was marked as canceled.

Anchor to replacementFulfillmentOrderreplacementFulfillmentOrder
•

The fulfillment order that was created to replace the canceled fulfillment order.

•

The list of errors that occurred from executing the mutation.

•
mutation

Marks an in-progress fulfillment order as incomplete, indicating the fulfillment service is unable to ship any remaining items, and closes the fulfillment request.

This mutation can only be called for fulfillment orders that meet the following criteria:

  • Assigned to a fulfillment service location,
  • The fulfillment request has been accepted,
  • The fulfillment order status is IN_PROGRESS.

This mutation can only be called by the fulfillment service app that accepted the fulfillment request. Calling this mutation returns the control of the fulfillment order to the merchant, allowing them to move the fulfillment order line items to another location and fulfill from there, remove and refund the line items, or to request fulfillment from the same fulfillment service again.

Closing a fulfillment order is explained in the fulfillment service guide.

Arguments

•
ID!required

The ID of the fulfillment order to mark as incomplete.

•

An optional reason for marking the fulfillment order as incomplete.


Fields

•

The fulfillment order that was marked as incomplete.

•

The list of errors that occurred from executing the mutation.

•
mutation

Changes the location which is assigned to fulfill a number of unfulfilled fulfillment order line items.

Moving a fulfillment order will fail in the following circumstances:

  • The fulfillment order is closed.
  • The destination location has never stocked the requested inventory item.
  • The API client doesn't have the correct permissions.

Line items which have already been fulfilled can't be re-assigned and will always remain assigned to the original location.

You can't change the assigned location while a fulfillment order has a request status of SUBMITTED, ACCEPTED, CANCELLATION_REQUESTED, or CANCELLATION_REJECTED. These request statuses mean that a fulfillment order is awaiting action by a fulfillment service and can't be re-assigned without first having the fulfillment service accept a cancellation request. This behavior is intended to prevent items from being fulfilled by multiple locations or fulfillment services.

How re-assigning line items affects fulfillment orders

First scenario: Re-assign all line items belonging to a fulfillment order to a new location.

In this case, the assignedLocation of the original fulfillment order will be updated to the new location.

Second scenario: Re-assign a subset of the line items belonging to a fulfillment order to a new location. You can specify a subset of line items using the fulfillmentOrderLineItems parameter (available as of the 2023-04 API version), or specify that the original fulfillment order contains line items which have already been fulfilled.

If the new location is already assigned to another active fulfillment order, on the same order, then a new fulfillment order is created. The existing fulfillment order is closed and line items are recreated in a new fulfillment order.

Arguments

Anchor to fulfillmentOrderLineItemsfulfillmentOrderLineItems
•

The fulfillment order line items to be moved. If left blank, all unfulfilled line items belonging to the fulfillment order are moved.

•
ID!required

The ID of the fulfillment order to be moved.

•
ID!required

The ID of the location where the fulfillment order will be moved.


Fields

Anchor to movedFulfillmentOrdermovedFulfillmentOrder
•

The fulfillment order which now contains the moved line items and is assigned to the destination location.

If the original fulfillment order doesn't have any line items which are fully or partially fulfilled, the original fulfillment order will be moved to the new location. However if this isn't the case, the moved fulfillment order will differ from the original one.

Anchor to originalFulfillmentOrderoriginalFulfillmentOrder
•

The final state of the original fulfillment order.

As a result of the move operation, the original fulfillment order might be moved to the new location or remain in the original location. The original fulfillment order might have the same status or be closed.

Anchor to remainingFulfillmentOrderremainingFulfillmentOrder
•

This field is deprecated.

•

The list of errors that occurred from executing the mutation.

•
mutation

Marks a scheduled fulfillment order as open.

Arguments

•
ID!required

The ID of the fulfillment order to mark as open.


Fields

•

The fulfillment order that was transitioned to open and is fulfillable.

•

The list of errors that occurred from executing the mutation.

•
mutation

Rejects a cancellation request sent to a fulfillment service for a fulfillment order.

Arguments

•
ID!required

The ID of the fulfillment order associated with the cancellation request.

•

An optional reason for rejecting the cancellation request.


Fields

•

The fulfillment order whose cancellation request was rejected.

•

The list of errors that occurred from executing the mutation.

•
mutation

Rejects a fulfillment request sent to a fulfillment service for a fulfillment order.

Arguments

•
ID!required

The ID of the fulfillment order associated with the fulfillment request.

•

An optional array of line item rejection details. If none are provided, all line items will be assumed to be unfulfillable.

Note: After the fulfillment request has been rejected, none of the line items will be able to be fulfilled. This field documents which line items specifically were unable to be fulfilled and why.

•

An optional reason for rejecting the fulfillment request.

•

The reason for the fulfillment order rejection.


Fields

•

The fulfillment order whose fulfillment request was rejected.

•

The list of errors that occurred from executing the mutation.

•
mutation

Sends a cancellation request to the fulfillment service of a fulfillment order.

Arguments

•
ID!required

The ID of the fulfillment order associated with the cancellation request.

•

An optional reason for the cancellation request.


Fields

•

The fulfillment order specified in the cancelation request.

•

The list of errors that occurred from executing the mutation.

•
mutation

Sends a fulfillment request to the fulfillment service of a fulfillment order.

Arguments

Anchor to fulfillmentOrderLineItemsfulfillmentOrderLineItems
•

The fulfillment order line items to be requested for fulfillment. If left blank, all line items of the fulfillment order are requested for fulfillment.

•
ID!required

The ID of the fulfillment order associated with fulfillment request.

•

An optional message for the fulfillment request.

•

Whether the customer should be notified when fulfillments are created for this fulfillment order.


Fields

Anchor to originalFulfillmentOrderoriginalFulfillmentOrder
•

The original fulfillment order intended to request fulfillment for.

Anchor to submittedFulfillmentOrdersubmittedFulfillmentOrder
•

The fulfillment order that was submitted to the fulfillment service. This will be the same as the original fulfillment order field. The exception to this is partial fulfillment requests or fulfillment request for cancelled or incomplete fulfillment orders.

Anchor to unsubmittedFulfillmentOrderunsubmittedFulfillmentOrder
•

This field will only be present for partial fulfillment requests. This will represent the new fulfillment order with the remaining line items not submitted to the fulfillment service.

•

The list of errors that occurred from executing the mutation.

•
mutation

Creates a fulfillment service.

Fulfillment service location

When creating a fulfillment service, a new location will be automatically created on the shop and will be associated with this fulfillment service. This location will be named after the fulfillment service and inherit the shop's address.

If you are using API version 2023-10 or later, and you need to specify custom attributes for the fulfillment service location (for example, to change its address to a country different from the shop's country), use the LocationEdit mutation after creating the fulfillment service.

Arguments

•
URL!required

The URL to send requests for the fulfillment service. The following considerations apply:

  • Shopify queries the callback_url/fetch_tracking_numbers endpoint to retrieve tracking numbers for orders, if trackingSupport is set to true.
  • Shopify queries the callback_url/fetch_stock endpoint to retrieve inventory levels, if inventoryManagement is set to true.
  • Shopify uses the callback_url/fulfillment_order_notification endpoint to send fulfillment and cancellation requests.
Anchor to fulfillmentOrdersOptInfulfillmentOrdersOptIn
•
BooleanDefault:true

Whether the fulfillment service uses the fulfillment order based workflow for managing fulfillments.

As of 2022-07 API version, the fulfillment order based workflow is the only way to manage fulfillments. As the migration is now finished, the fulfillmentOrdersOptIn property is deprecated and is always set to true on correctly functioning fulfillment services.

The fulfillmentOrdersOptIn input field is deprecated and will be removed in the next API version. This API version makes it optional and defaults to true for a smooth migration experience. Do not set the fulfillmentOrdersOptIn argument, and you are ready for the next API version release.

•
BooleanDefault:false

Whether the fulfillment service manages product inventory and provides updates to Shopify.

•
String!required

The name of the fulfillment service.

•
BooleanDefault:false

Whether the fulfillment service can stock inventory alongside other locations.

•
BooleanDefault:false

Whether the fulfillment service provides tracking numbers for packages.


Fields

•

The created fulfillment service.

•

The list of errors that occurred from executing the mutation.

•
mutation

Deletes a fulfillment service.

Arguments

Anchor to destinationLocationIddestinationLocationId
•

The ID of an active merchant managed location where inventory and commitments will be relocated after the fulfillment service is deleted.

Inventory will only be transferred if the TRANSFER inventory action has been chosen.

•
ID!required

The ID of the fulfillment service to delete.

•

The action to take with the location after the fulfillment service is deleted.


Fields

•

The ID of the deleted fulfillment service.

•

The list of errors that occurred from executing the mutation.

•
mutation

Updates a fulfillment service.

If you are using API version 2023-10 or later, and you need to update the location managed by the fulfillment service (for example, to change the address of a fulfillment service), use the LocationEdit mutation.

Arguments

•

The URL to send requests for the fulfillment service. The following considerations apply:

  • Shopify queries the callback_url/fetch_tracking_numbers endpoint to retrieve tracking numbers for orders, if trackingSupport is set to true.
  • Shopify queries the callback_url/fetch_stock endpoint to retrieve inventory levels, if inventoryManagement is set to true.
  • Shopify uses the callback_url/fulfillment_order_notification endpoint to send fulfillment and cancellation requests.
Anchor to fulfillmentOrdersOptInfulfillmentOrdersOptIn
•
Boolean

Whether the fulfillment service uses the fulfillment order based workflow for managing fulfillments.

As of 2022-07 API version, the fulfillment order based workflow is the only way to manage fulfillments, and true is the only valid value for fulfillmentOrdersOptIn.

•
ID!required

The id of the fulfillment service.

•

Whether the fulfillment service tracks product inventory and provides updates to Shopify.

•

The name of the fulfillment service.

•
Boolean

Whether the fulfillment service can stock inventory alongside other locations.

•

Whether the fulfillment service provides tracking numbers for packages.


Fields

•

The updated fulfillment service.

•

The list of errors that occurred from executing the mutation.

•
mutation

Updates tracking information for a fulfillment.

Arguments

•
ID!required

The ID of the fulfillment.

•

Whether the customer will be notified of this update and future updates for the fulfillment. If this field is left blank, then notifications won't be sent to the customer when the fulfillment is updated.

•

The tracking input for the mutation, including tracking URL, number, and company.


Fields

•

The updated fulfillment with tracking information.

•

The list of errors that occurred from executing the mutation.

•
mutation

Update a gift card.

Arguments

•
ID!required

The ID of the gift card to be updated.

•

The input fields to update the gift card.


Fields

•

The updated gift card.

•

The list of errors that occurred from executing the mutation.

•
mutation

Activate an inventory item at a location.

Arguments

•

The initial available quantity of the inventory item being activated at the location.

•
ID!required

The ID of the inventory item to activate.

•
ID!required

The ID of the location of the inventory item being activated.

•

The initial on_hand quantity of the inventory item being activated at the location.

Anchor to stockAtLegacyLocationstockAtLegacyLocation
•
BooleanDefault:false

Allow activation at or away from fulfillment service location with sku sharing off. This will deactivate inventory at all other locations.


Fields

•

The inventory level that was activated.

•

The list of errors that occurred from executing the mutation.

•
mutation

Removes an inventory item's quantities from a location, and turns off inventory at the location.

Arguments

•
ID!required

The ID of the inventory level to deactivate.


Fields

•

The list of errors that occurred from executing the mutation.

•
mutation

Updates an inventory item.

Arguments

•
ID!required

The ID of the inventory item to update.

•

The input fields that update an inventoryItem.


Fields

•

The inventory item that was updated.

•

The list of errors that occurred from executing the mutation.

•
mutation

Create new marketing activity.

Arguments

•

The Input of marketing activity create.


Fields

•

The created marketing activity.

•

The path to return back to shopify admin from embedded editor.

•

The list of errors that occurred from executing the mutation.

•
mutation

Updates a marketing activity with the latest information.

Arguments

•

The Input of the marketing activity.


Fields

•

The updated marketing activity.

•

The redirect path from the embedded editor to the Shopify admin.

•

The list of errors that occurred from executing the mutation.

•
mutation

Deletes multiple metafields in bulk.

Arguments

•

A list of identifiers specifying metafields to delete. At least one identifier must be specified.


Fields

•

List of metafield identifiers that were deleted, null if the corresponding metafield isn't found.

•

The list of errors that occurred from executing the mutation.

•
mutation

Cancels an order.

Arguments

•
BooleanDefault:false

Whether to send a notification to the customer about the order cancellation.

•
ID!required

The ID of the order to be canceled.

•

The reason for canceling the order.

•
Boolean!required

Indicates whether to refund the amount paid by the customer. Authorized payments will be voided regardless of this setting.

•
Boolean!required

Whether to restock the inventory committed to the order. For unpaid orders fulfilled from locations that have been deactivated, inventory will not be restocked to the deactivated locations even if this argument is set to true.

•
StringDefault:null

A staff-facing note about the order cancellation. This is not visible to the customer.


Fields

•

The job that asynchronously cancels the order.

Anchor to orderCancelUserErrorsorderCancelUserErrors
•

The list of errors that occurred from executing the mutation.

•
[UserError!]!non-null

The list of errors that occurred from executing the mutation.

•
mutation

Captures payment for an authorized transaction on an order. An order can only be captured if it has a successful authorization transaction. Capturing an order will claim the money reserved by the authorization. orderCapture can be used to capture multiple times as long as the OrderTransaction is multi-capturable. To capture a partial payment, the included amount value should be less than the total order amount. Multi-capture is available only to stores on a Shopify Plus plan.

Arguments

•

The input for the mutation.


Fields

•

The created capture transaction.

•

The list of errors that occurred from executing the mutation.

•
mutation

Closes an open order.

Arguments

•

The input for the mutation.


Fields

•

The closed order.

•

The list of errors that occurred from executing the mutation.

•
mutation

Adds a custom line item to an existing order. For example, you could add a gift wrapping service as a custom line item. To learn how to edit existing orders, refer to Edit an existing order with Admin API.

Arguments

•
ID!required

The ID of the calculated order to which the custom item is added.

•

The ID of the retail location (if applicable) from which the custom item is sold. Used for tax calculations. A default location will be chosen automatically if none is provided.

•
MoneyInput!required

The unit price of the custom item. This value can't be negative.

•
Int!required

The quantity of the custom item. This value must be greater than zero.

•

Whether the custom item requires shipping. Defaults to false.

•

Whether the custom item is taxable. Defaults to true.

•
String!required

The name of the custom item to add.


Fields

•

The custom line item that will be added to the order based on the current edits.

•

An order with the edits applied but not saved.

•

The list of errors that occurred from executing the mutation.

•
mutation

Adds a discount to a line item on the current order edit. For more information on how to use the GraphQL Admin API to edit an existing order, refer to Edit existing orders.

Arguments

•

The discount to add to the line item.

•
ID!required

The ID of the calculated order to update.

•
ID!required

The ID of the calculated line item to add the discount to.


Fields

Anchor to addedDiscountStagedChangeaddedDiscountStagedChange
•

The discount applied to a line item during this order edit.

•

The line item with the edits applied but not saved.

•

An order with the edits applied but not saved.

•

The list of errors that occurred from executing the mutation.

•
mutation

Adds a line item from an existing product variant. As of API version 2025-04, the orderEditAddVariant API will respect the contextual pricing of the variant.

Arguments

•
BooleanDefault:false

Whether the mutation can create a line item for a variant that's already on the calculated order.

•
ID!required

The ID of the calculated order to edit.

•

The ID of the location to check for inventory availability. A default location ID is chosen automatically if none is provided.

•
Int!required

The quantity of the item to add to the order. Must be a positive value.

•
ID!required

The ID of the variant to add.


Fields

•

The calculated line item that's added during this order edit.

•

The calculated order with the edits applied but not saved.

•

The list of errors that occurred from executing the mutation.

•
mutation

Starts editing an order. Mutations are operating on OrderEdit. All order edits start with orderEditBegin, have any number of orderEdit* mutations made, and end with orderEditCommit.

Arguments

•
ID!required

The ID of the order to begin editing.


Fields

•

The order that will be edited.

•

The list of errors that occurred from executing the mutation.

•
mutation

Applies and saves staged changes to an order. Mutations are operating on OrderEdit. All order edits start with orderEditBegin, have any number of orderEdit* mutations made, and end with orderEditCommit.

Arguments

•
ID!required

The ID of the calculated order that will have its changes applied to the order.

•

Whether to notify the customer or not.

•

Note for staff members.


Fields

•

The order with changes applied.

•

The list of errors that occurred from executing the mutation.

•
mutation

Sets the quantity of a line item on an order that is being edited. For more information on how to use the GraphQL Admin API to edit an existing order, refer to Edit existing orders.

Arguments

•
ID!required

The ID of the calculated order to edit. The edit changes the quantity on the line item.

•
ID!required

The ID of the calculated line item to edit.

•
ID

The ID of the location. If 'restock' is set to true, the restocked item will be made available at the specified location.

•
Int!required

The new quantity to set for the line item. This value cannot be negative.

•

Whether or not to restock the line item when the updated quantity is less than the original quantity.


Fields

•

The calculated line item with the edits applied but not saved.

•

The calculated order with the edits applied but not saved.

•

The list of errors that occurred from executing the mutation.

•
mutation

Marks an order as paid. You can only mark an order as paid if it isn't already fully paid.

Arguments

•

The input for the mutation.


Fields

•

The order marked as paid.

•

The list of errors that occurred from executing the mutation.

•
mutation

Opens a closed order.

Arguments

•

The input for the mutation.


Fields

•

The opened order.

•

The list of errors that occurred from executing the mutation.

•
mutation

Updates the attributes of an order, such as the customer's email, the shipping address for the order, tags, and metafields associated with the order.

If you need to make significant updates to an order, such as adding or removing line items, changing quantities, or modifying discounts, then use the orderEditBegin mutation instead. The orderEditBegin mutation initiates an order editing session, allowing you to make multiple changes before finalizing them. Learn more about using the orderEditBegin mutation to edit existing orders.

Learn how to build apps that integrate with order management and fulfillment processes.

Arguments

•
OrderInput!required

The attributes of the updated order.


Fields

•

The updated order.

•

The list of errors that occurred from executing the mutation.

•
mutation

Creates a new componentized product.

Arguments

•

Input for creating a componentized product.


Fields

Anchor to productBundleOperationproductBundleOperation
•

The asynchronous ProductBundleOperation creating the componentized product.

•

The list of errors that occurred from executing the mutation.

•
mutation

Updates a componentized product.

Arguments

•

Input for updating a componentized product.


Fields

Anchor to productBundleOperationproductBundleOperation
•

The asynchronous ProductBundleOperation updating the componentized product.

•

The list of errors that occurred from executing the mutation.

•
mutation

Creates a product with attributes such as title, description, and vendor. You can use the productCreate mutation to define options and values for products with product variants, such as different sizes or colors.

To create multiple product variants for a single product and manage prices, use the productVariantsBulkCreate mutation.

To create or update a product in a single request, use the productSet mutation.

Learn more about the product model and adding product data.

Arguments

•
ProductInput

The properties of the new product.

•

The media to add to the product.

•

The attributes of the new product.


Fields

•

The product object.

•
Shop!non-null

The shop associated with the product.

•

The list of errors that occurred from executing the mutation.

•
mutation

Deletes a product, including all associated variants and media.

As of API version 2023-01, if you need to delete a large product, such as one that has many variants that are active at several locations, you may encounter timeout errors. To avoid these timeout errors, you can instead use the asynchronous ProductDeleteAsync mutation.

Arguments

•

Specifies the product to delete by its ID.

•
BooleanDefault:true

Specifies whether or not to run the mutation synchronously.


Fields

•

The ID of the deleted product.

Anchor to productDeleteOperationproductDeleteOperation
•

The product delete operation, returned when run in asynchronous mode.

•
Shop!non-null

The shop associated with the product.

•

The list of errors that occurred from executing the mutation.

•
mutation

Duplicates a product.

If you need to duplicate a large product, such as one that has many variants that are active at several locations, you might encounter timeout errors.

To avoid these timeout errors, you can instead duplicate the product asynchronously.

In API version 2024-10 and higher, include synchronous: false argument in this mutation to perform the duplication asynchronously.

In API version 2024-07 and lower, use the asynchronous ProductDuplicateAsyncV2.

Metafield values are not duplicated if the unique values capability is enabled.

Arguments

•
BooleanDefault:false

Specifies whether or not to duplicate images.

•
BooleanDefault:false

Specifies whether or not to duplicate translations.

•

The new status of the product. If no value is provided the status will be inherited from the original product.

•
String!required

The new title of the product.

•
ID!required

The ID of the product to be duplicated.

•
BooleanDefault:true

Specifies whether or not to run the mutation synchronously.


Fields

•

The asynchronous job that duplicates the product images.

•

The duplicated product.

Anchor to productDuplicateOperationproductDuplicateOperation
•

The product duplicate operation, returned when run in asynchronous mode.

•
Shop!non-null

The user's shop.

•

The list of errors that occurred from executing the mutation.

•
mutation

Asynchronously reorders the media attached to a product.

Arguments

•
ID!required

The ID of the product on which to reorder medias.

•

A list of moves to perform which will be evaluated in order.


Fields

•

The asynchronous job which reorders the media.

•

The list of errors that occurred from executing the mutation.

•
[UserError!]!non-null

The list of errors that occurred from executing the mutation.

•
mutation

Updates a product.

For versions 2024-01 and older: If you update a product and only include some variants in the update, then any variants not included will be deleted.

To safely manage variants without the risk of deleting excluded variants, use productVariantsBulkUpdate.

If you want to update a single variant, then use productVariantUpdate.

Arguments

•
ProductInput

The updated properties for a product.

•

List of new media to be added to the product.

•

The updated properties for a product.


Fields

•

The updated product object.

•

The list of errors that occurred from executing the mutation.

•
mutation

Publishes a resource to a channel. If the resource is a product, then it's visible in the channel only if the product status is active. Products that are sold exclusively on subscription (requiresSellingPlan: true) can be published only on online stores.

Arguments

•
ID!required

The resource to create or update publications for.

•

Specifies the input fields required to publish a resource.


Fields

•

Resource that has been published.

•
Shop!non-null

The user's shop.

•

The list of errors that occurred from executing the mutation.

•
mutation

Publishes a resource to current channel. If the resource is a product, then it's visible in the channel only if the product status is active. Products that are sold exclusively on subscription (requiresSellingPlan: true) can be published only on online stores.

Arguments

•
ID!required

The resource to create or update publications for.


Fields

•

Resource that has been published.

•
Shop!non-null

The user's shop.

•

The list of errors that occurred from executing the mutation.

•
mutation

Unpublishes a resource from a channel. If the resource is a product, then it's visible in the channel only if the product status is active.

Arguments

•
ID!required

The resource to delete or update publications for.

•

Specifies the input fields required to unpublish a resource.


Fields

•

Resource that has been unpublished.

•
Shop!non-null

The user's shop.

•

The list of errors that occurred from executing the mutation.

•
mutation

Unpublishes a resource from the current channel. If the resource is a product, then it's visible in the channel only if the product status is active.

Arguments

•
ID!required

The resource to delete or update publications for.


Fields

•

Resource that has been unpublished.

•
Shop!non-null

The user's shop.

•

The list of errors that occurred from executing the mutation.

•
mutation

Creates a refund.

Arguments

•
RefundInput!required

The input fields that are used in the mutation for creating a refund.


Fields

•

The order associated with the created refund.

•

The created refund.

•

The list of errors that occurred from executing the mutation.

•
mutation

Creates a saved search.

Arguments

•

Specifies the input fields for a saved search.


Fields

•

The saved search that was created.

•

The list of errors that occurred from executing the mutation.

•
mutation

Delete a saved search.

Arguments

•

The input fields to delete a saved search.


Fields

Anchor to deletedSavedSearchIddeletedSavedSearchId
•

The ID of the saved search that was deleted.

•
Shop!non-null

The shop of the saved search that was deleted.

•

The list of errors that occurred from executing the mutation.

•
mutation

Updates a saved search.

Arguments

•

The input fields to update a saved search.


Fields

•

The saved search that was updated.

•

The list of errors that occurred from executing the mutation.

•
mutation

Theme app extensions

Your app might not pass App Store review if it uses script tags instead of theme app extensions. All new apps, and apps that integrate with Online Store 2.0 themes, should use theme app extensions, such as app blocks or app embed blocks. Script tags are an alternative you can use with only vintage themes. Learn more.

Script tag deprecation

Script tags will be sunset for the Order status page on August 28, 2025. Upgrade to Checkout Extensibility before this date. Shopify Scripts will continue to work alongside Checkout Extensibility until August 28, 2025.

Creates a new script tag.

Arguments

•

The input fields for a script tag.


Fields

•

The script tag that was created.

•

The list of errors that occurred from executing the mutation.

•
mutation

Theme app extensions

Your app might not pass App Store review if it uses script tags instead of theme app extensions. All new apps, and apps that integrate with Online Store 2.0 themes, should use theme app extensions, such as app blocks or app embed blocks. Script tags are an alternative you can use with only vintage themes. Learn more.

Script tag deprecation

Script tags will be sunset for the Order status page on August 28, 2025. Upgrade to Checkout Extensibility before this date. Shopify Scripts will continue to work alongside Checkout Extensibility until August 28, 2025.

Deletes a script tag.

Arguments

•
ID!required

The ID of the script tag to delete.


Fields

•

The ID of the deleted script tag.

•

The list of errors that occurred from executing the mutation.

•
mutation

Theme app extensions

Your app might not pass App Store review if it uses script tags instead of theme app extensions. All new apps, and apps that integrate with Online Store 2.0 themes, should use theme app extensions, such as app blocks or app embed blocks. Script tags are an alternative you can use with only vintage themes. Learn more.

Script tag deprecation

Script tags will be sunset for the Order status page on August 28, 2025. Upgrade to Checkout Extensibility before this date. Shopify Scripts will continue to work alongside Checkout Extensibility until August 28, 2025.

Updates a script tag.

Arguments

•
ID!required

The ID of the script tag to update.

•

Specifies the input fields for a script tag.


Fields

•

The script tag that was updated.

•

The list of errors that occurred from executing the mutation.

•
mutation

Creates a segment.

Arguments

•
String!required

The name of the segment to be created. Segment names must be unique.

•
String!required

A precise definition of the segment. The definition is composed of a combination of conditions on facts about customers such as email_subscription_status = 'SUBSCRIBED' with this syntax.


Fields

•

The newly created segment.

•

The list of errors that occurred from executing the mutation.

•
mutation

Deletes a segment.

Arguments

•
ID!required

Specifies the segment to delete.


Fields

•

ID of the deleted segment.

•

The list of errors that occurred from executing the mutation.

•
mutation

Updates a segment.

Arguments

•
ID!required

Specifies the segment to be updated.

•

The new name for the segment.

•

A precise definition of the segment. The definition is composed of a combination of conditions on facts about customers such as email_subscription_status = 'SUBSCRIBED' with this syntax.


Fields

•

The updated segment.

•

The list of errors that occurred from executing the mutation.

•
mutation

Deletes a shipping package.

Arguments

•
ID!required

The ID of the shipping package to remove.


Fields

•

The ID of the deleted shipping package.

•

The list of errors that occurred from executing the mutation.

•
mutation

Set a shipping package as the default. The default shipping package is the one used to calculate shipping costs on checkout.

Arguments

•
ID!required

The ID of the shipping package to set as the default.


Fields

•

The list of errors that occurred from executing the mutation.

•
mutation

Updates a shipping package.

Arguments

•
ID!required

The ID of the shipping package to update.

•

Specifies the input fields for a shipping package.


Fields

•

The list of errors that occurred from executing the mutation.

•
mutation

Deletes a locale for a shop. This also deletes all translations of this locale.

Arguments

•
String!required

ISO code of the locale to delete.


Fields

•

ISO code of the locale that was deleted.

•

The list of errors that occurred from executing the mutation.

•
mutation

Adds a locale for a shop. The newly added locale is in the unpublished state.

Arguments

•
String!required

ISO code of the locale to enable.

Anchor to marketWebPresenceIdsmarketWebPresenceIds
•

The list of markets web presences to add the locale to.


Fields

•

ISO code of the locale that was enabled.

•

The list of errors that occurred from executing the mutation.

•
mutation

Updates a locale for a shop.

Arguments

•
String!required

ISO code of the locale to update.

•

Specifies the input fields for a shop locale.


Fields

•

The locale that was updated.

•

The list of errors that occurred from executing the mutation.

•
mutation

Creates staged upload targets for each input. This is the first step in the upload process. The returned staged upload targets' URL and parameter fields can be used to send a request to upload the file described in the corresponding input.

For more information on the upload process, refer to Upload media to Shopify.

Arguments

•

The information required to generate staged upload targets.


Fields

•

The staged upload targets that were generated.

•

The list of errors that occurred from executing the mutation.

•
mutation

Creates a storefront access token for use with the Storefront API.

An app can have a maximum of 100 active storefront access tokens for each shop.

Get started with the Storefront API.

Arguments

•

Provides the input fields for creating a storefront access token.


Fields

•
Shop!non-null

The user's shop.

Anchor to storefrontAccessTokenstorefrontAccessToken
•

The storefront access token.

•

The list of errors that occurred from executing the mutation.

•
mutation

Deletes a storefront access token.

Arguments

•

Provides the input fields required to delete a storefront access token.


Fields

Anchor to deletedStorefrontAccessTokenIddeletedStorefrontAccessTokenId
•

The ID of the deleted storefront access token.

•

The list of errors that occurred from executing the mutation.

•
mutation

Add tags to an order, a draft order, a customer, a product, or an online store article.

Arguments

•
ID!required

The ID of a resource to add tags to.

•
[String!]!required

A list of tags to add to the resource. Can be an array of strings or a single string composed of a comma-separated list of values. Example values: ["tag1", "tag2", "tag3"], "tag1, tag2, tag3".


Fields

•

The object that was updated.

•

The list of errors that occurred from executing the mutation.

•
mutation

Remove tags from an order, a draft order, a customer, a product, or an online store article.

Arguments

•
ID!required

The ID of the resource to remove tags from.

•
[String!]!required

A list of tags to remove from the resource in the form of an array of strings. Example value: ["tag1", "tag2", "tag3"].


Fields

•

The object that was updated.

•

The list of errors that occurred from executing the mutation.

•
mutation

Asynchronously delete URL redirects in bulk.

•

The asynchronous job removing the redirects.

•

The list of errors that occurred from executing the mutation.

•
mutation

Creates a new webhook subscription.

Building an app? If you only use app-specific webhooks, you won't need this. App-specific webhook subscriptions specified in your shopify.app.toml may be easier. They are automatically kept up to date by Shopify & require less maintenance. Please read About managing webhook subscriptions.

Arguments

•

The type of event that triggers the webhook.

•

Specifies the input fields for a webhook subscription.


Fields

•

The list of errors that occurred from executing the mutation.

•

The webhook subscription that was created.

•
mutation

Deletes a webhook subscription.

Building an app? If you only use app-specific webhooks, you won't need this. App-specific webhook subscriptions specified in your shopify.app.toml may be easier. They are automatically kept up to date by Shopify & require less maintenance. Please read About managing webhook subscriptions.

Arguments

•
ID!required

The ID of the webhook subscription to delete.


Fields

Anchor to deletedWebhookSubscriptionIddeletedWebhookSubscriptionId
•

The ID of the deleted webhook subscription.

•

The list of errors that occurred from executing the mutation.

•
mutation

Updates a webhook subscription.

Building an app? If you only use app-specific webhooks, you won't need this. App-specific webhook subscriptions specified in your shopify.app.toml may be easier. They are automatically kept up to date by Shopify & require less maintenance. Please read About managing webhook subscriptions.

Arguments

•
ID!required

The ID of the webhook subscription to update.

•

Specifies the input fields for a webhook subscription.


Fields

•

The list of errors that occurred from executing the mutation.

•

The webhook subscription that was updated.

Deprecated mutations

•
mutation

Publishes a collection to a channel.

Arguments

•

Specify a collection to publish and the sales channels to publish it to.


Fields

•

The published collection.

Anchor to collectionPublicationscollectionPublications
•

The channels where the collection has been published.

•
Shop!non-null

The shop associated with the collection.

•

The list of errors that occurred from executing the mutation.

•
mutation

Unpublishes a collection.

Arguments

•

Specify a collection to unpublish and the sales channels to remove it from.


Fields

•

The collection that has been unpublished.

•
Shop!non-null

The shop associated with the collection.

•

The list of errors that occurred from executing the mutation.

•
mutation

Creates a merchant checkout for the given draft order.

Arguments

•
ID!required

Specifies the Draft order's id that we create the checkout for.


Fields

•

The list of errors that occurred from executing the mutation.

•
mutation

Creates a fulfillment for one or many fulfillment orders. The fulfillment orders are associated with the same order and are assigned to the same location.

Arguments

•

The input fields used to create a fulfillment from fulfillment orders.

•

An optional message for the fulfillment request.


Fields

•

The created fulfillment.

•

The list of errors that occurred from executing the mutation.

•
mutation

Updates tracking information for a fulfillment.

Arguments

•
ID!required

The ID of the fulfillment.

•

Whether the customer will be notified of this update and future updates for the fulfillment. If this field is left blank, then notifications won't be sent to the customer when the fulfillment is updated.

•

The tracking input for the mutation, including tracking URL, number, and company.


Fields

•

The updated fulfillment with tracking information.

•

The list of errors that occurred from executing the mutation.

•
mutation

Deletes a metafield.

Arguments

•

Fields

•

The ID of the deleted metafield.

•

The list of errors that occurred from executing the mutation.

•
mutation

Creates a MetafieldStorefrontVisibility record to make all metafields that belong to the specified resource and have the established namespace and key combination visible in the Storefront API.

Arguments

•

Specifies the input fields for a MetafieldStorefrontVisibility record.


Fields

Anchor to metafieldStorefrontVisibilitymetafieldStorefrontVisibility
•

The MetafieldStorefrontVisibility that was created.

•

The list of errors that occurred from executing the mutation.

•
mutation

Deletes a MetafieldStorefrontVisibility record. All metafields that belongs to the specified record will no longer be visible in the Storefront API.

Arguments

•
ID!required

The ID of the MetafieldStorefrontVisibility record to delete.


Fields

Anchor to deletedMetafieldStorefrontVisibilityIddeletedMetafieldStorefrontVisibilityId
•

The ID of the deleted MetafieldStorefrontVisibility record.

•

The list of errors that occurred from executing the mutation.

•
mutation

Removes a line item discount that was applied as part of an order edit.

Arguments

Anchor to discountApplicationIddiscountApplicationId
•
ID!required

The ID of the calculated discount application to remove.

•
ID!required

The ID of the calculated order from which to remove the discount.


Fields

•

The calculated line item after removal of the discount.

•

An order with the edits applied but not saved.

•

The list of errors that occurred from executing the mutation.

•
mutation

Deletes a private metafield. Private metafields are automatically deleted when the app that created them is uninstalled.

Arguments

•

The input fields for the private metafield to delete.


Fields

Anchor to deletedPrivateMetafieldIddeletedPrivateMetafieldId
•

The ID of private metafield that was deleted.

•

The list of errors that occurred from executing the mutation.

•
mutation

Creates or updates a private metafield. Use private metafields when you don't want the metafield data to be accessible by merchants or other apps. Private metafields are accessible only by the application that created them and only from the GraphQL Admin API.

An application can create a maximum of 10 private metafields per shop resource.

Arguments

•

Specifies the input fields for the private metafield.


Fields

•

The private metafield that was created or updated.

•

The list of errors that occurred from executing the mutation.

•
mutation

Creates media for a product.

Arguments

•

List of new media to be added to a product.

•
ID!required

Specifies the product associated with the media.


Fields

•

The newly created media.

•

The list of errors that occurred from executing the mutation.

•

The product associated with the media.

•
[UserError!]!non-null

The list of errors that occurred from executing the mutation.

•
mutation

Deletes media for a product.

Arguments

•
[ID!]!required

The media IDs to be deleted.

•
ID!required

Specifies the product ID from which the media will be deleted.


Fields

•

List of media IDs which were deleted.

Anchor to deletedProductImageIdsdeletedProductImageIds
•

List of product image IDs which were deleted.

•

The list of errors that occurred from executing the mutation.

•

The product associated with the deleted media.

•
[UserError!]!non-null

The list of errors that occurred from executing the mutation.

•
mutation

Publishes a product. Products that are sold exclusively on subscription (requiresSellingPlan: true) can only be published on online stores.

Arguments

•

Specifies the product to publish and the channels to publish it to.


Fields

•

The product that has been published.

•
Shop!non-null

The user's shop.

•

The list of errors that occurred from executing the mutation.

•

The channels where the product is published.

•
mutation

Unpublishes a product.

Arguments

•

Specifies the product to unpublish and the channel to unpublish it from.


Fields

•

The product that has been unpublished.

•
Shop!non-null

The user's shop.

•

The list of errors that occurred from executing the mutation.

•
mutation

Updates media for a product.

Arguments

•

A list of media updates.

•
ID!required

Specifies the product on which media will be updated.


Fields

•

The updated media object.

•

The list of errors that occurred from executing the mutation.

•

The product on which media was updated.

•
[UserError!]!non-null

The list of errors that occurred from executing the mutation.

•
mutation

Generates the URL and signed paramaters needed to upload an asset to Shopify.

Arguments

•

The input fields for generating a staged upload.


Fields

•

The signed parameters that can be used to upload the asset.

•
String!non-null

The signed URL where the asset can be uploaded.

•

The list of errors that occurred from executing the mutation.

•
mutation

Uploads multiple images.

Arguments

•

The input fields for generating staged uploads.


Fields

•

The staged upload targets that were generated.

•

The list of errors that occurred from executing the mutation.


Was this section helpful?


Was this section helpful?