How to find out if confluence server REST API uses prototype or context in URIs?

[stonecoldcrazyx]

So I've tried to use basic REST call on my local server instance started version 6.4.3 from atlassian SDK with atlas-run-standalone command, and it works like a charm

curl u admin:admin "http://myVmName:1990/confluence/rest/api/content"  | python -mjson.tool

I get a JSON answer and it's all nice. Also works when I type URI in a browser.

Now, at work we also use confluence, one test instance and one prod let's call it. Test is on version 6.6.2 and prod on 6.4.3 (like the one I used in SDK). On both of them similar curl call doesn't work - says page not found. Instances are behind HTTPS so I call curl with -k and -L also (I don't know if there's any loadbalancers or something in front of them). When I'm logged in in browser I try the same thing and get same answer. Now, I've managed to find somewhere the older "prototype" api and I've managed to get 

https://confluence.myCompany.domain/rest/prototype/1/content/57934140

where 57934140 is ID of an existing page and that works!!

So my question is? What is the difference, some configuration, settings, missing something? Once again, same confluence versions 6.4.3 - standalone one and SDK. In the docs it says that API is applicable to Confluence server 5.5 and later.

Is the problem related to "context" mentioned here? How can I find out should I use it or not?

[Minh Tran]

I replied the answer for this question here https://community.atlassian.com/t5/Confluence-questions/How-to-find-out-if-confluence-server-REST-API-uses-prototype-or/qaq-p/761692#M103485