Path for graph explore endpooint is not the one documented

Hi there,
I have recently started to experiment with the graph api on elastic cloud.
There was a major blocker. In the documentation the api is exposed at:


but in elastic cloud, running elasticsearch 5.3 the api is actually exposed at:


adding a _ to graph.

Is this the intended behaviour and the documentation and all the clients (we tested python and javascript) are outdated, or is it a bug/elastic cloud specific environment change?



That sounds like a documentation error, not anything Cloud specific - well spotted, thanks for reporting

I'll move this topic over to the xpack forum so it catches the eyes of the right people!


thanks, apparently is also already fixed in the master branch of the python client, but perhaps is not released yet...

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.