Add requestedEditResolve mutation for order edit resolution

7/16/2026, 12:00:18 AM

The Shopify GraphQL API introduces a new mutation, requestedEditResolve, that allows merchants or third‑party apps to mark a requested edit on an order as completed.
The input for this mutation is a non‑null RequestedEditResolveInput which requires the ID of the requested edit to resolve.
The mutation returns a RequestedEditResolvePayload that contains the resolved RequestedEdit object and a list of any userErrors.
User errors are represented by RequestedEditResolveUserError and must implement the DisplayableError interface, with a code and an optional list of field paths.
The available error codes are NOT_FOUND when the requested edit ID cannot be located, and INVALID when the input is malformed.
The mutation does not modify any queries or remove existing types, and can be safely integrated alongside existing order management mutations.

Mutation Changes

➕ Added Mutations (1)

requestedEditResolve

Resolves a requested edit on an order, marking it as completed.

Type Changes

➕ Added Types (4)

📥RequestedEditResolveInput➕ AddedINPUT_OBJECT

The input fields for resolving a requested edit.

🏗️RequestedEditResolvePayload➕ AddedOBJECT

Return type for requestedEditResolve mutation.

Fields: requestedEdit, userErrors
🏗️RequestedEditResolveUserError➕ AddedOBJECT

Errors related to resolving a requested edit.

Fields: code, field, message
📋RequestedEditResolveUserErrorCode➕ AddedENUM

Possible error codes that can be returned by RequestedEditResolveUserError.

Values: NOT_FOUND, INVALID