How to Generate a Jira API Token: 5 Simple Steps in 2026
Need to connect an app to Jira? Learn how to generate jira api token in 5 simple steps and authenticate safely. Read now to get started.
A Jira API token lets an app or script access Jira Cloud without using your account password. Creating one takes only a few minutes, but a careless setup can expose your account or leave an integration broken when the token expires.
If you’re trying to connect a reporting script, automation, or integration, unclear token settings can make a simple task frustrating. A token may also grant more access than you intended, or stop working after its expiration date. Here’s how to create one, authenticate safely, and check that it works. I’ll also explain what to do if you use Jira Data Center, since its authentication process is different.
How to Generate a Jira API Token in 5 Steps
To generate a Jira API token, sign in to your Atlassian account, create a token in its security settings, then use it with your account email to authenticate Jira Cloud API requests.
-

Confirm you’re using Jira Cloud
These steps apply to Jira Cloud accounts, which usually have an address like your-team.atlassian.net. You’ll need an Atlassian account with access to the Jira site you want to connect.
If your organization runs Jira Data Center, pause here. Data Center authentication usually uses personal access tokens instead, so the Cloud token manager may not be available to you.
-
Open your Atlassian security settings
Sign in to the Atlassian account associated with your Jira access. Then open Atlassian’s API token settings.
You can also reach the settings through your Atlassian account profile by selecting Security and looking for the API token section. If you manage several Atlassian accounts, check the signed-in email before continuing.
-
Create a token with a clear name and suitable access
Select the option to create an API token. Atlassian may offer a standard token or an option to create a token with scopes. The available choices can vary as Atlassian updates its account settings.
Give the token a name that identifies its purpose, such as weekly-jira-report. If you choose scopes, grant only the access the integration needs. Some integrations may require a standard token, so check their setup instructions before choosing.
Set an expiration date if prompted. A shorter period can reduce the risk of an old credential remaining active, though you’ll need to replace it before it expires.
-
Copy and store the token securely
After you create the token, copy it and save it in an approved password manager or secrets manager. Atlassian may show the full value only once. If you close the page without saving it, you’ll need to create another token.
Don’t paste the token into a public code repository, a shared chat, or a script that other people can read. Treat it like a password: anyone who obtains it may be able to make API requests with your account’s permissions.
-
Authenticate a Jira Cloud API request
For Jira Cloud, API token authentication commonly uses Basic authentication with your Atlassian account email as the username and the token as the password. Store both values in protected environment variables, then test with a low-risk endpoint:
curl -u "$ATLASSIAN_EMAIL:$ATLASSIAN_API_TOKEN" "https://your-team.atlassian.net/rest/api/3/myself"
Replace the site address with your own Jira Cloud address. A successful response confirms that the credentials work and identifies the authenticated account. It doesn’t grant additional Jira permissions; the account still needs access to the requested Jira content.
What a Jira API Token Does—and What It Doesn’t
A Jira API token is a credential for connecting a program or integration to Jira Cloud. It acts in the context of your Atlassian account, so the access it can use is tied to that account’s Jira permissions.
For example, a script using your token can request issue details that your account is allowed to view. The token doesn’t automatically make the script an administrator or let it bypass project permissions.
But here’s the truth: a token is still a sensitive credential. If another person gets it, they may be able to make API requests as your account until you revoke it or it expires.
Choose Scopes and Expiration Carefully
Scopes can restrict the actions a token is allowed to perform when you create a scoped token. The integration you’re configuring may need only read access, or it may need permission to create or update Jira issues.
Here’s why: granting broader access than necessary increases the impact of accidental exposure. If a weekly report only reads issue details, avoid permissions that would let it edit or delete issues.
Expiration is another part of the setup. For instance, a token created for a short project can have an end date that matches the project’s expected duration. Add a reminder to replace it before it expires, especially if a team relies on the integration.
Keep the Token Safe After Setup
Store the token in a protected secrets manager or another approved credential vault. Avoid putting it directly in a script, a command that gets saved in shell history, or a public code repository.
Let me explain: a token can keep working even after the person who created it forgets where it was used. Keep a short record of the integration’s owner, purpose, and renewal date so you can identify it later.
Limit access to the stored credential to people and services that need it. If the integration changes owners, review whether the existing token should be replaced or revoked.
Check the Authentication Method Before Troubleshooting
A Jira Cloud API token and a Jira Data Center personal access token are not interchangeable. If your Jira address is managed within your organization rather than on an atlassian.net site, ask your administrator which authentication method is enabled.
You might be wondering: why does the distinction matter? The token creation process, authentication format, and available API endpoints can differ between Cloud and Data Center deployments. Following Cloud steps for a Data Center site may produce an authentication error even when your credentials are correct.
Also check the integration’s own requirements. Some tools support scoped tokens, while others may need a standard token or a different authentication method. Follow the instructions for your specific Jira deployment and integration.
Jira API Token Management with ONES.com
ONES.com is a unified platform for project management and knowledge management, powered by ONES Assistant. ONES Project handles project management, while ONES Wiki provides knowledge management; the products are sold separately.

If your team is reviewing Jira alternatives, ONES Project is an option to evaluate for project work. Its Jira-compatible workflows can help teams familiar with Jira assess a different platform, though workflow compatibility does not mean Jira API tokens work with ONES.
Core capabilities
- When plugin dependencies complicate project work: ONES Project includes built-in reporting, so teams can review project progress without relying on as many separate plugins.
- When a team needs workflows tailored to its process: Custom workflows and fields let teams shape how work moves through their projects and what information they track.
- When sprint planning needs a dedicated structure: Sprint management supports teams that organize work into planned development cycles.
- When routine actions consume time: Automation can handle configured repeatable tasks, giving team members more time for work that needs their attention.
- When Jira familiarity matters during evaluation: Jira-compatible workflows can make it easier for a Jira team to assess how its working patterns might fit in ONES Project.
- When a team wants project and knowledge management in one platform: ONES.com brings ONES Project and ONES Wiki together as platform offerings, while each product remains separately available.
- When deployment requirements vary: ONES.com is available in Cloud, On-Premise, Private Cloud, and Air-gapped deployments, giving organizations options for different environments.
- When self-hosting is required: The self-hosted version has full feature parity with the cloud version, so teams can assess deployment needs without assuming a reduced feature set.
Application scenarios
A product team that currently manages issues in Jira could assess ONES Project when it wants to review workflow flexibility, sprint management, and built-in reporting together. The team should assess its actual integration and authentication requirements separately rather than assume existing Jira tokens will carry over.
An organization with restricted network requirements could compare Cloud, On-Premise, Private Cloud, and Air-gapped deployment options. If the team also needs a dedicated knowledge base, it can assess ONES Wiki separately from ONES Project.
Common Jira API Token Challenges
The token is rejected
Problem: A request returns an authentication error even though you have a token. Try this: Confirm that you’re using the Atlassian account email paired with the token, that the token hasn’t expired or been revoked, and that the site address is correct.
The integration can’t access an issue
Problem: Authentication succeeds, but a request can’t read a particular issue. Try this: Check the Atlassian account’s access to that project and issue. A token uses its account’s permissions, so successful authentication alone doesn’t guarantee access to every project.
The integration doesn’t accept a scoped token
Problem: Your tool rejects a token created with scopes. Try this: Check the tool’s Jira Cloud setup instructions and confirm which token types it supports. If it requires another type, follow your organization’s security process before creating a replacement.
The token expires unexpectedly
Problem: A scheduled task stops working after a period of normal operation. Try this: Check the token’s expiration date and replace it through the integration’s approved credential process. Update the stored value, test a request, then revoke the old token when it’s no longer needed.
FAQs
Can I use a Jira API token instead of my Atlassian password?
Yes. Jira Cloud API requests commonly use your Atlassian account email and an API token for Basic authentication. This lets an integration authenticate without using your account password. Store the token securely and follow the integration’s setup guidance, since some tools may support different token types or authentication methods.
Can one API token be used for multiple Jira integrations?
A token may work with more than one integration, but separate tokens make access easier to review and revoke. For example, if a reporting service and a build process use distinct tokens, you can replace one credential without disrupting the other. Use your organization’s credential policy to decide how tokens should be assigned and managed.
What should I do if I lose the token value?
You generally can’t retrieve the full value after leaving the token creation screen. Create a replacement token, update the integration’s protected credential, and test the connection. Once the replacement works, revoke the lost token if you can identify it in your Atlassian account’s token settings.
Do Jira API tokens work with Jira Data Center?
Atlassian account API tokens are intended for Jira Cloud. Jira Data Center commonly uses personal access tokens, if that option is enabled by the organization’s administrator. Check your deployment type and ask your administrator about the supported authentication method before creating credentials.
Conclusion
To generate a Jira API token, open your Atlassian security settings, create a token with an appropriate name and access level, save it securely, and test it with a Jira Cloud API request.
Keep the token private, track its expiration, and remember that it uses the permissions of the Atlassian account that created it. If authentication still fails, confirm your deployment type and the integration’s requirements before making another token.
A few careful setup choices can prevent a routine connection from becoming a security risk or an unexpected outage. When you’re assessing how your team manages projects, ONES Project is one Jira alternative to evaluate, with its own workflow and deployment considerations.