You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The (Swagger?) API documentation pages served up by the server display the API version number (e.g. 3.0) but not the release number of the server code (e.g. 7.8.2). Making the server version readily available would simplify accurate reporting of bugs and feature requests.
My request is to have the server version tag displayed on every API documentation page, ideally in the header.
In the page footer would also work, but as the page header includes other reference information such as the API version and the link to documentation, this seems like the obvious place to put it.
The text was updated successfully, but these errors were encountered:
Thank you for reporting this feature request.
I agree this would be a great addition to the server API docs and we will investigate how this could be integrated.
In the meantime, please refer to the following endpoint to figure out the version of the server you are working with:
The (Swagger?) API documentation pages served up by the server display the API version number (e.g. 3.0) but not the release number of the server code (e.g. 7.8.2). Making the server version readily available would simplify accurate reporting of bugs and feature requests.
My request is to have the server version tag displayed on every API documentation page, ideally in the header.
In the page footer would also work, but as the page header includes other reference information such as the API version and the link to documentation, this seems like the obvious place to put it.
The text was updated successfully, but these errors were encountered: