Confluence's REST API is protected by the same restrictions which are provided via Confluence's standard web interface. This means that if you do not log in, you are accessing Confluence anonymously. Furthermore, if you log in and do not have permission to view something in Confluence, you will not be able to view it using the Confluence REST API either.
In most cases, the first step in using the Confluence REST API is to authenticate a user account with your Confluence site. Any authentication that works against Confluence will work against the REST API. On this page we will show you a simple example of basic authentication.
Most client software provides a simple mechanism for supplying a user name (the Atlassian account email) and password (the API token) and will build the required authentication headers automatically. For example, you can specify the argument with cURL as follows:
1 2 3 4 5
curl -D- \ -u email@example.com:user_api_token \ -X GET \ -H "Content-Type: application/json" \ https://your-domain.atlassian.net/rest/api/2/issue/createmeta
You can use Postman to make calls to the Confluence Cloud REST APIs. Check it out: Confluence Cloud REST API.
If you need to you may construct and send basic auth headers yourself. To do this you need to perform the following steps:
1 2 3 4 5
curl -D- \ -X GET \ -H "Authorization: Basic dXNlcjp1c2Vy" \ -H "Content-Type: application/json" \ "https://your-domain.atlassian.net/rest/api/2/issue/QA-31"
Because Confluence permits a default level of access to anonymous users, it does not supply a typical authentication challenge. Some HTTP client software expect to receive an authentication challenge before they will send an authorization header. This means that Confluence may not behave as your HTTP client software expects. In this case, you may need to configure it to supply the authorization header, as described above, rather than relying on its default mechanism.