/components/schemas/Package does not exist in Sandbox interactive API documentation
Friday, February 5, 2021 at 06:02amI'm trying to looking up the documentation for the POST /api/packages call within the Interactive API Definitions page in the sandbox environment, but when I click on this method, the page displays the following error:
Resolver error at paths./api/packages.post.requestBody.content.application/json.schema.$ref
Could not resolve reference: Could not resolve pointer: /components/schemas/Package does not exist in document
Attached is a screen dump of what's displayed at the top of the page.
Can anyone suggest an alternative location from where I can get the details of the /components/schemas/Package schema?
Reply to: /components/schemas/Package does not exist in Sandbox interactive API documentation
Friday, February 5, 2021 at 06:56amHi paultipper,
Thanks for bringing it up to us! I can reproduce the same and seems the API schema is unexpectedly broken in this yaml version. I will report to the team and reply back to you very soon!
Duo
Reply to: Hi paultipper, Thanks…
Friday, February 5, 2021 at 06:59amHi Duo,
Thanks for the speedy reply. Is there a previous, unbroken version of the schema available anywhere that I could look at in the meantime?
Regards,
Paul
Reply to: /components/schemas/Package does not exist in Sandbox interactive API documentation
Friday, February 5, 2021 at 07:51amHi paultipper,
Attached is the yaml file for 11.37 version. I will update this thread once the latest version is ready!
Duo
Reply to: /components/schemas/Package does not exist in Sandbox interactive API documentation
Friday, February 5, 2021 at 09:22amBrilliant, Duo - thanks very much! :)
Reply to: Brilliant, Duo - thanks very…
Monday, February 8, 2021 at 08:39amHi Paul,
The yaml file has been updated in the interactive API doc, and now the issue should be fixed!
Duo
Reply to: Hi Paul, The yaml file…
Tuesday, February 9, 2021 at 03:02amHi Duo,
Yes, I can see the schema now in the documentation - thanks for resolving this!
Regards,
Paul