General information

A primary use case for API tokens is to allow scripts to access REST APIs for Confluence applications using HTTP basic authentication.

If you define a token for a user, only that user can use it. If you do not specify a user, any user will be able to use this token.

If an external system is compromised, you can revoke the token instead of changing the password and consequently changing it in all scripts and integrations.

How does it work

Depending on the details of the HTTP library you use, simply replace your password with the token. For example, when using curl, you could do something like this:

Note that:

• USER here is the email address or user name.

• TOKEN here is token generated in REST API Tokens page

CURL Example

Postman Example

Note that :

• Basic Auth use this type in Authorization type

• Username here is the email address or user name.

• Passwordhere is token generated in REST API Tokens page

Specify supported URLs/methods for tokens

You can limit the token to specific urls and methods. Provide endpoint url with regular expression, add (or not) method restriction.

You can define any number of token restrictions, each of which should be on a new line.

Examples:

• Restriction to set property endpoint on space with key EXTENDER (only POST method)

• Restriction to all space endpoints (for all methods)

Changes