Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG][SP-API] Reports API is not working as intended to documentations. #2842

Closed
caner-cetin opened this issue Nov 12, 2022 · 9 comments
Closed

Comments

@caner-cetin
Copy link

{"reportType":"GET_MERCHANTS_LISTINGS_FYP_REPORT","marketplaceIds":"[ATVPDKIKX0DER]"}

When I send this body data to /reports/2021-06-30/reports WITHOUT NO PARAMETERS BECAUSE THIS IS WHAT YOU DOCUMENT , I get

{ "errors": [ { "code": "InvalidInput", "message": "One or more required parameters missing", "details": "marketplaceIds;" } ] }

but according to documentation only required thing is body data.
image

See also #1349

#235

@caner-cetin caner-cetin changed the title Reports API is not working as intended to documentations. [BUG][SP-API] Reports API is not working as intended to documentations. Nov 12, 2022
@caner-cetin
Copy link
Author

Also see #2195

@caner-cetin
Copy link
Author

image

don't rely on AWS or SP-API documentation at all, in the end, you will always fix your problem at the stack overflow or issues tab over here. congrats on making the worst documentation work for developers.

See #2155, he couldnt make it because content-type was never documented there.

See #1681, where in the world "encode the params in the url path" is documented in SP-API? Also it doesnt work.

See #1246, that dude couldnt even solve the problem because there were no details on what was wrong, so future readers cant also figure out what was wrong and fix our problems inspired by that.

you. are. worst. api. developers. ever. ever.

@caner-cetin
Copy link
Author

caner-cetin commented Nov 13, 2022

See also #2039

I fixed my issue with sending

"marketplaceIds":["ATVPDKIKX0DER"]

instead of

"marketplaceIds":ATVPDKIKX0DER

So what, send the report ID back to amazon servers? Hell nah fella.

image

It seems like

{"reportId":"500XXXXX"}

needs to be combinated with something as it doest accept it and it isnt clearly stated in documentation again, GOD, profanity ME.

@caner-cetin
Copy link
Author

image

What does this even mean? WHAT? HOW?

@stefnats
Copy link

Seems like you are confusing reportId and reportDocumentId. ReportId is usually a number and reportDocumentId is a longer string.
When you create (request) a report you will receive a reportId.
When this report is finished, reports api will return reportDocumentId alongside the reportId.
With reportDocumentId you can request the download url for the report.

I hope this clarifies it a bit better.

@rejeenald
Copy link

@stefnats what about when requesting the download URL, it returns Access to requested resource is denied. This never happened before, but suddenly it did. I never changed anything, except that I make the request on the next day.

@stefnats
Copy link

Access to requested resource is denied

is this error happening when you call the URL that you obtained the day before?
So: Did you call getReportDocument, saved the url and download the next day?

In that case i would think that this is caused, because the URL that was returned might be available only for a certain short time period. If you want a new link you have to call it again.
Again, this is just a guess.

@github-actions
Copy link

This is a very old issue that is probably not getting as much attention as it deserves. We encourage you to check if this is still an issue after the latest release and if you find that this is still a problem, please feel free to open a new issue and make a reference to this one.

@github-actions
Copy link

github-actions bot commented Jun 1, 2023

closed for inactivity

@github-actions github-actions bot closed this as completed Jun 1, 2023
@shreeharsh-a shreeharsh-a transferred this issue from amzn/selling-partner-api-docs May 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants