Skip to Main Content

PGX REST API Docs outdated

Alastair ParagasJul 20 2017 — edited Aug 20 2020

It seems like the REST API docs are outdated? I am looking at the docs located at  and noticed that by judging the API calls the PGX Java client library makes (currently using 2.4.1), it seems like some of the paths don't match up.

For example, the API docs documents the /future endpoint with the following, but it seems like /future/core is a new accessible route that isn't documented. Another example is the /core endpoint, where it seems like the library is making a POST-based call to /core/graph to create a graph when in the documentation, it suggests POST-ing at /core/session/{sessionId}/graph to create a graph:

Screen Shot 2017-07-20 at 10.15.29 AM.png

Screen Shot 2017-07-20 at 10.17.46 AM.png

Screen Shot 2017-07-19 at 4.37.33 PM.png

Also, trying to understand and determine the kind of JSON requests that should be made at certain paths and the expected JSON responses is quite hairy considering that the request and response schemas are in verbose XML. Are there currently any plans in improving the REST API docs so that clients can be made for other languages besides NodeJS and Java?

This post has been answered by unknown-3038109 on Jul 20 2017
Jump to Answer
Post Details
Added on Jul 20 2017
1 comment