Currently, the public API produced from the CMS isn't all that helpful if you don't know the exact routes for your GET requests.
I would eventually like to see things be more helpful. For example, if I hit /api it should tell me all available routes from there, which would currently be /v1.
And if I hit a GET request to /api/v1/ instead of not returning anything, it could tell me all of the available routes from there, which would be for content type routes, users, etc.
I imagine SEO folks would say this is better for Google indexing, as well.
Currently, the public API produced from the CMS isn't all that helpful if you don't know the exact routes for your
GETrequests.I would eventually like to see things be more helpful. For example, if I hit
/apiit should tell me all available routes from there, which would currently be/v1.And if I hit a
GETrequest to/api/v1/instead of not returning anything, it could tell me all of the available routes from there, which would be for content type routes, users, etc.I imagine SEO folks would say this is better for Google indexing, as well.