[GraphQL] Missing mutation to share wishlist via email

[lintots]

Preconditions and environment

Magento 2.4.x with Wishlist GraphQL enabled.
Currently, Magento's GraphQL API allows creating, updating, and deleting wishlists and wishlist items. However, there is no available GraphQL mutation to share a wishlist via email, which is a core feature available in Magento’s storefront (Luma) via standard HTTP POST.

Steps to reproduce

• Install Magento 2.4.x with Wishlist GraphQL module enabled (Magento_WishlistGraphQl is core since 2.4.0).
• Create a Customer and Login using Customer Token via GraphQL.
• Create a Wishlist and add products using GraphQL mutations:
  1. createWishlist
  2. addProductsToWishlist
• Try to find a GraphQL mutation to share the wishlist via email.

Observe that:
No such mutation (shareWishlist) exists in the GraphQL schema.
Sharing is only possible via the Magento frontend (wishlist/shared/send/) using HTTP POST (controller-based).

Expected result

A GraphQL mutation like shareWishlist should be available. It should accept parameters like:

• wishlist_id or wishlist_uid
• emails (list of email addresses)
• message (optional)
  Expected mutation
  mutation {
  shareWishlist(
  input: {
  wishlist_uid: "xxx",
  emails: ["test@example.com"],
  message: "Check out my wishlist!"
  }
  ) {
  success
  }
  }

Actual result

No such mutation is available. Sharing a wishlist is only possible via traditional Magento PHP controllers (wishlist/shared/send/ route).
Impact:

• Cannot implement full wishlist features in PWA or headless applications.
• Breaks UX consistency between frontend and headless apps.
• Forces developers to build workarounds outside GraphQL standards.

Additional information

Suggestion:
Introduce a shareWishlist mutation as part of Magento_WishlistGraphQl module.

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @lintots. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant]

Hi @engcom-November. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-November]

Hello @lintots ,

Thanks for your reporting and collaboration.

We gone through with the description and it seems to be a Enhancement to proceed further marking this as Feature Request

Thanks.