New SP-API documentation format... extremely confusing? What happened to user friendly real world example JSON code? (See AWD createInbound example) #4884
Unanswered
MetaMan2023
asked this question in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
It seems recently the SP-API documentation system has changed to a new format.
The old system, while it had some bugs, was overall very user friendly to read -- the new format seems like a "self serve". For example I'm trying to program AWD SP-API "createInbound" and struggling to get an example JSON data set to work from.
It seems I have to literally drill down through dozens of nested parameter boxes, enter fake info just to get a sample JSON -- and it's very confusing. My resulting example winds up with like 10 nested levels of "distributionPackage".
What happened to the old user friendly, human readable example documentation -- is it gone forever? What would have taken 10 minutes is now a complete mess and I don't know how to proceed or follow this.
Example here:
To get an example of body parameter JSON object seems to be a nightmare. Am I missing something?
-John
Beta Was this translation helpful? Give feedback.
All reactions