Creation of Service account in jira

[Ayush Pathak]

Hi, I want to create a centric service account which does not required pass n all.
so that it can be used for integrations activities with other platforms where i can use that service account to create API. 

[Trudy Claspill]

Hello @Ayush Pathak 

That is not possible.

With Jira Cloud all accounts, whether "service" or for real people, require an Atlassian Cloud account.

If you are not integrating with an Authorization and Authentication service (like Active Directory) for provisioning users and authenticating them, then you would have to use the Atlassian Cloud web pages for creating a new Atlassian Cloud account. That will require that a password be set and a valid (and unique) email address be provided to which a confirmation email can be sent and responded to.

For interacting with Atlassian Cloud product APIs you will have to authenticate the user. That can include providing an API token. I'm not a complete expert on that, but I believe the only way to generate a token is to login to Atlassian Cloud as that account and manually generate the token. (I could be wrong. Things may have changed since the last time I had to do that.) I don't believe it is possible to generate the token for another account, such as logging in as an Organization Admin and then generating a token that would be used by Account/User X.

[Darryl Lee]

Hey @Ayush Pathak ! 

@Trudy Claspill very ably and accurately answered your question back in May, but we thought you might want to know that since that time, Atlassian has indeed introduced Service Accounts (caveat: unless you have Atlassian Guard Standard or an Enterprise subscription, you only get FIVE of these.) 

These Service Accounts do not, as you noted, have passwords, and in fact, can only be used to create API tokens.

You can read the announcement from August 2025 here:

• Build safer, smarter integrations with service accounts 

And here's the documentation:

• Understand service accounts 
• Manage API tokens for service accounts 

Important things to note (aside from the limits above):

• Scopes matter!
  You would not believe how many times I've had to recreate tokens because I got the scopes wrong. ALSO you cannot edit scopes after creating a token. ALSO you (inexplicably) cannot VIEW the scopes of an existing token. SO yeah, maybe take a screenshot or copy/paste the summary of scopes for each token before you leave that screen.
  
  
• ENDPOINTS ARE DIFFERENT!
  This is a huge one. With your personal API tokens (and IN ALL THE DOCUMENTATION), you use: https://YOURSITE.atlassian.net/rest
  
  Well, in their "wisdom", Atlassian has made Service Accounts live "outside" of your instance's directory, and SO, you have to use a different endpoint for the APIs. 
  
  So like API docs above note, you will need to use:
  https://api.atlassian.com/ex/jira/{cloudId}/rest
  
  Yes, this means if you test your code using personal API tokens, you will need to update it to use a different endpoint for the service account. Fun times. :-/
  
  (To find your Cloud ID: 
  https://<my-site-name>.atlassian.net/_edge/tenant_info)

ANYWAYS though, those caveats aside, we've been very happy to not burn licenses for Service Accounts AND have a separate directory for them that easily allows us to see what people are doing.

Additionally, because we are using Entra SSO, our service accounts needed to be provisioned by our IT department, so there was a lag, AND we had to deal with the hassle of password sharing, etc etc.