amzn / selling-partner-api-models

This repository contains OpenAPI models for developers to use when developing software to call Selling Partner APIs.
Apache License 2.0
590 stars 728 forks source link

[BUG] [SP-API] [Issue] createInboundPlan requires phoneNumber #654

Closed MojoJake closed 4 months ago

MojoJake commented 4 months ago

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report  
[ ] Feature request
[ ] Documentation issue or request
[ ] Other... Please describe:

SP-API Name and Version or Report/Feed Type

/inbound/fba/2024-03-20/inboundPlans/createInboundPlan

Expected Behavior

createInboundPlan didn't used to require a phone number as part of the sourceAddress. The documentation doesn't mention phoneNumber at all for the "sourceAddress" https://developer-docs.amazon.com/sp-api/docs/fulfillment-inbound-api-v2024-03-20-reference#createinboundplanrequest

Current Behavior

createInboundPlan fails whether I provide a phone number or not. It returns: "1 validation error detected: Value null at 'request.sourceAddress.phoneNumber' failed to satisfy constraint: Member must not be null"

Context/Screenshots

Your Environment

I am using the node npm package.

shantikolli commented 4 months ago

Same issue, im also facing..created an issue https://github.com/amzn/selling-partner-api-models/issues/650

ssamran15 commented 4 months ago

I am having the same issue, no matter what you do you'll receive this same error. furthermore, I am also getting 500 internal server error in getShipment and item/quantity issue in setPackingInformation. so yeah it seems like the API is still under development.

KirillChekalin commented 4 months ago

📢 Update: createInboundPlan API Now Working Without Phone Number Hi everyone!

I wanted to share an update for those of us using the createInboundPlan API. 🎉

What happened? Previously, many of us encountered an error when creating an inbound plan, which indicated that the phoneNumber field in the sourceAddress was mandatory. This was unexpected since the documentation did not list this field as required.

Good news! Today, I discovered that this issue has been resolved. The phone number is no longer required in the request to create an inbound plan, and the API now works as documented.

or-en commented 4 months ago

This issue has returned

[400] 1 validation error detected: Value null at 'request.sourceAddress.phoneNumber' failed to satisfy constraint: Member must not be null (InvalidInput)

Anyone had it as well?

111L12 commented 4 months ago

[400] 1 validation error detected: Value null at 'request.sourceAddress.phoneNumber' failed to satisfy constraint: Member must not be null (InvalidInput)

111L12 commented 4 months ago

[400] 1 validation error detected: Value null at 'request.sourceAddress.phoneNumber' failed to satisfy constraint: Member must not be null (InvalidInput)

111L12 commented 4 months ago

此问题又回来了

[400] 检测到 1 个验证错误:“request.sourceAddress.phoneNumber”处的值为 null 无法满足约束:成员不得为 null (InvalidInput)

有人也有吗?

I also encountered this problem today. Have you solved it?

miraemor commented 4 months ago

Still experiencing validation error. Neither of requests is valid (with or without "phoneNumber" in sourceAddress section)

shreeharsh-a commented 4 months ago

Please reach out to developer support so that we can better help you with issues related to SP API.

Note: SP API or docs related issues / troubleshooting support is managed by a different team. We can help if the issue is related to the content published on this repo.

shantikolli commented 4 months ago

@shreeharsh-a Many a times I have reached to developer support, created cases but there is no proper information provided. I have created one case which is with the support team from almost 5 days, yet there is no update. Any issue is raised, all they are doing is to provide the documentation link which is not useful as every one working on SP-API API endpoints are already aware of the documentation and following the same.