POST /V1/customers api issue

[ShehzadAhm]

Preconditions and environment

• Magento version 2.4.5-P8
• Should have at least one website

Steps to reproduce

1. Create an integration and get the access token
2. Using the token, make a call to POST /V1/customers API to create customer

Expected result

• https://example.magento.test/rest/<store_code>/V1/customers api should work

Actual result

Getting 400 Bad request error:
{
"message": "Specified request cannot be processed."
}

Additional information

API Documentation: https://developer.adobe.com/commerce/webapi/rest/tutorials/orders/order-create-customer/

But the api works if the endpoint is: <magento_url>/<store_view_code>/rest/V1/customers (client project)

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 @ShehzadAhm. 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. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• 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.

[ShehzadAhm]

@magento give me 2.4.5-p8 instance

[magento-deployment-service]

Hi @ShehzadAhm. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @ShehzadAhm, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.

[ShehzadAhm]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @ShehzadAhm. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @ShehzadAhm, here is your Magento Instance: https://c21f89084bf10a7a63d9aeadcaf917e3.instances-prod.magento-community.engineering
Admin access: https://c21f89084bf10a7a63d9aeadcaf917e3.instances-prod.magento-community.engineering/admin_dc41
Login: ad4f1d0f
Password: 3e021a79750f

[ShehzadAhm]

Tested with the provided instance:
POST <magento-url>/rest/<store_code>/V1/customers throws error

POST <magento-url>/rest/<store_view_code>/V1/customers works fine

However, the first API endpoint is given in the documentation.

[NOTE: In my client project, only this endpoint is working: <magento_url>/<store_view_code>/rest/V1/customers!]

[m2-assistant]

Hi @engcom-Delta. 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

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - 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-Delta]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @engcom-Delta. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @engcom-Delta, here is your Magento Instance: https://c21f89084bf10a7a63d9aeadcaf917e3.instances-prod.magento-community.engineering
Admin access: https://c21f89084bf10a7a63d9aeadcaf917e3.instances-prod.magento-community.engineering/admin_705a
Login: 3fab4f8b
Password: 44f723cd8104

[engcom-Delta]

Hi @ShehzadAhm ,

Thanks for your reporting and collaboration.
We have verified the issue in latest 2.4-develop instance and it is reproducible.
Hence, Confirming the issue.

Steps to reproduce -

1. Create one or multiple websites.
   
2. Generate Access Token
3. Run Create Customer API with store code.
   
   Observe Error displays when user provide store code.
4. Now, Run Create Customer API with store view code.
   
   API runs successfully with store view code but displays error with store code.

As per dev doc -

Thanks.

[github-jira-sync-bot]

Unfortunately, not enough information was provided to create a Jira ticket. Please make sure you added the following label(s): Reproduced on 2.4.x, ^Area:.*

Once all required labels are present, please add Issue: Confirmed label again.

[github-jira-sync-bot]

Unfortunately, not enough information was provided to create a Jira ticket. Please make sure you added the following label(s): Reproduced on 2.4.x, ^Area:.*

Once all required labels are present, please add Issue: Confirmed label again.

[github-jira-sync-bot]

Unfortunately, not enough information was provided to create a Jira ticket. Please make sure you added the following label(s): Reproduced on 2.4.x, ^Area:.*

Once all required labels are present, please add Issue: Confirmed label again.

[github-jira-sync-bot]

✅ Jira issue https://jira.corp.adobe.com/browse/AC-12677 is successfully created for this GitHub issue.

[m2-assistant]

✅ Confirmed by @engcom-Delta. Thank you for verifying the issue.
Issue Available: @engcom-Delta, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[github-jira-sync-bot]

❌ Cannot export the issue. This GitHub issue is already linked to Jira issue(s): https://jira.corp.adobe.com/browse/AC-12677

[github-jira-sync-bot]

❌ Cannot export the issue. This GitHub issue is already linked to Jira issue(s): https://jira.corp.adobe.com/browse/AC-12677

[engcom-Delta]

Hi @ShehzadAhm ,

Thanks for your reporting and collaboration. We are closing the ticket as issue is related to dev docs.
You can refer AdobeDocs/commerce-webapi#351 to see the updates.

Thanks.