Create an API token for a self-hosted Confluence installation?
Asked by Michael Woffenden:

Regarding [creating an API token](https://confluence.atlassian.com/cloud/api-tokens-938839638.html), is there any way to create an API token for a self-hosted (server) Confluence installation?

The need is to [connect Zapier to Confluence,](https://zapier.com/apps/confluence/integrations) which requires this.

Zapier's documention states: "Confluence Cloud and **Server 5.5+** are supported."


Answers:
author: Shannon S
body: Hi Michael,

Generating a token is only supported in the Cloud API.

Using Server you will need to authenticate. Have a look at [Confluence Server REST API](https://developer.atlassian.com/server/confluence/confluence-server-rest-api/) for more details.

Regards,

Shannon

comments: author: Michael Woffenden
body: Thanks Shannon - But I do not see any information about authenticating on the link you sent. Where might I see those details?


author: Shannon S
body: Hi Michael,

[REST API Examples](https://developer.atlassian.com/server/confluence/confluence-rest-api-examples/) on the left-hand side does show some examples, but have a look here as well:

* [Using the REST API](https://developer.atlassian.com/server/confluence/using-the-rest-apis-prototype-only/)

> You can authenticate yourself for the REST APIs in two ways:

*
  > **Log in to Confluence manually.** You will then be authenticated for the REST APIs for that same browser session.
*
  > **Use HTTP basic authentication** (Authorization HTTP header) containing '`Basic username:password`'. Please note however, `username:password` must be base64 encoded. The URL must also contain the '`os_authType=basic`' query parameter.

Let me know if you have any questions.

Regards,

Shannon


author: Gunnarsson Johan _2_
body: Five years later, this summer our username+password authentication stopped working, we have an on-prem installation of Atlassian Confluence, and found this article:

<https://developer.atlassian.com/cloud/confluence/deprecation-notice-basic-auth/>

I understand this as we would not be affected??? Still we cannot authenticate anymore with either user+password or with user+accesstoken and all the required magic wand stuff.

*Which APIs and methods will be restricted?* {#toc-hId--437287049}
------------------------------------------------------------------

*For the following APIs and pages, all requests using basic authentication with a non-API token credential will return 401 (Unauthorized) after the deprecation period:*

* *Confluence ++**Cloud**++public REST API*
* *All Confluence ++**Cloud**++web pages*

How are we supposed to mainatain our REST API integrations?


author: Christian Reichert (resolution)
body: Hi Michael,

this may be too old now for you to benefit - however it may still be worth for someone who stumbles across this topic.

We have released a 3rd party App that implements the API Token Concept in Confluence \& Jira.

* [API Token Authentication for Jira](https://marketplace.atlassian.com/apps/1221586/api-token-authentication-for-jira?hosting=server)
* [API Token Authentication for Confluence](https://marketplace.atlassian.com/apps/1221608/api-token-authentication-for-confluence?hosting=server)

It's available for both Server \& Data-Center. It also has some additional security features (blocking normal basic auth, IP address restrictions, etc) that some people may find interesting.

Cheers,  
Chris

P.S. Full disclosure, I work for [resolution, a marketplace vendor.](https://marketplace.atlassian.com/vendors/1210947/resolution-reichert-network-solutions-gmbh)


Tags: api

confluence-server

token