Open rabbiveesh opened 1 year ago
Okay, so I got it to work by changing the MIME type of my request to application/json
. The openapi spec needs to be fixed, this is ridiculous
Hi @rabbiveesh , thank you for bringing this to our attention. We’ve amended the spec for the /sb/themes
endpoints to display the application/json
content type for the request. This issue also alerted us to some similar inaccuracies elsewhere in the Sponsored Brands specification, and fixes for those bugs are pending.
Thank you for expressing your frustration, both with the documentation error and with the Content-Type versioning system used in some of our APIs. We'll be sure to relay your feedback to the engineering teams as well.
Thanks for your patience! I'm usually a bit more polite with these things, sorry for dumping on you.
There's also an issue with some endpoints that they don't list the mandatory headers (at the very least /sb/themes/list
is missing) and it trips up my client generator
Can you tell me which api I am getting from which campaign report I am seeing on Amazon console, I am getting wrong campaign from version 2 of api and it has migrated to version 3 because I am getting the campaign from that api. I get more data from the Advertising Console than from the Campaigns report
If you need help troubleshooting a problem with the Amazon Ads API, visit the Amazon Ads API service desk. Issues are for reporting documentation bugs and requesting enhancements only.
Describe the bug The endpoint for
/sb/themes/list
is not correct.URL of the content https://advertising.amazon.com/API/docs/en-us/sponsored-brands/3-0/openapi#tag/Theme-targeting/operation/sbListThemes
Description of what the documentation currently says The documentation says that it's meant to consume the content-type
application/vnd.sbthemeslistrequest.v3+json
and return the content typeapplication/vnd.sbthemeslistresponse.v3+json
. However, when calling with those content types, I always get a 415 error, which implies that it's supposed to be some other MIME type. Sooooo, which is it?Parenthetically, making the APIs work only with these weird vendor MIME types has only caused pain + heartache.