`url` property served in api responses is incomplete about privatebin HOT 3 CLOSED

It provides the path to the API endpoint on the same domain. It will only prepend the URL base to the webservers request URI:

In the example setup (privatebin.net) the API endpoint is at / and PHP's JSON serializer chooses to be a bit more strict and escapes the slash (see JSON spec, search for "escape"), hence the url getting encoded as \/?[id].

from privatebin.

Is this perhaps for a case where the post API endpoint is different from the get API endpoint?

If not, doesn't the paste poster already know the path of the API endpoint when they are making the post request?
Given the API endpoint (1) (known while making post) and this API (2) I don't see how this URL property adds any new information. The client can construct the full url from those pieces (1,2) of info already. Am I missing something?

Also, when making comments, the "url" returned is currently misleading, yes? Because going to that url doesn't really give back the comment.

from privatebin.

The API endpoint is always the same (including for human visitors - the only difference is the non-default, server side yourls-proxy). The difference lies in the different payloads and HTTP request types.

from privatebin.