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
547 stars 722 forks source link

Validation issue while posting inboundplan - Fulfillment Inbound API v2024-03-20 #650

Closed shantikolli closed 2 months ago

shantikolli commented 2 months ago

Hi

As per the documentation, there is no phone Number required for source address during inbound plan. I posed without phoneNumber and it throws validation as

{ "errors": [ { "code": "InvalidInput", "message": "1 validation error detected: Value null at 'request.sourceAddress.phoneNumber' failed to satisfy constraint: Member must not be null", "details": "" } ] }

I thought may be the documentation missed this information so I tried to include the phone number and post the request. Again it throws the same validation

attaching the screenshots withoutPhone withphone

KirillChekalin commented 2 months ago

i'm having the same issue.

garply1 commented 2 months ago

Same here. The fulfillment Inbound isn't even close to being ready. I can't believe it was even released as "early/preview".

ssamran15 commented 2 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 2 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.

shantikolli commented 2 months ago

@KirillChekalin Thank you for the update. Yes, I see that it works now. Its quite surprising that the documentation is not consistent. If the issue is fixed, they should at least update. I created a case yesterday and I didnt receive any update from Amazon support team.

or-en commented 1 month 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?

shantikolli commented 1 month ago

@or-en Looks like then it is working intermittently, strange!!

garply1 commented 1 month ago

The bug is back. At least this time you can add phoneNumber to your schema and it will work. Last time if failed no matter whether is was included or not.

ElvinsSun commented 1 month ago

I have add phoneNumber to sourceAddress.But get errors.Regardless of whether phonenumber is empty or not

shreeharsh-a commented 1 month ago

@puppsupr

puppsupr commented 1 month ago

Hi, We have a new release and change in the model for additional functionalities. Please try to import the new model and retry which should resolve the issues.