Hi Pierluigi,
My apologies for the late response.
Path queries can be executed through the HTTP API, in fact, that’s how Stardog clients (Studio and CLI) execute them. The problem, however, is that there’s currently no standardized format for serializing path result sets in HTTP responses.
Stardog server sends back paths as tuples using the same format as for SELECT queries. Each binding set represents a single edge in a path. Empty tuples are used as path separators. The format is basically what you’d see in Studio or CLI in the tabular output.
Another caveat is that variable names for the results are sent back in the following format: [{variables occurring in the start pattern}, start variable, edge variables, end variable, {variables occurring in the end pattern}]. The start and end variables also occur in the start and end pattern so they’re repeated.
Everything else, e.g. the endpoint, etc., should be the same as for SELECT queries.
Cheers,
Pavel