How to Create a Jira API Token: 5 Steps That Work Today
Is your Jira integration stuck? Learn how to create jira api token in five steps and test it securely. Read now to get connected.
A Jira integration can’t connect, an automation is stuck, or a script keeps asking for credentials. You may know an API token is involved, but Atlassian’s account settings and token options can make the next step unclear.
Using your password instead can expose your account and may fail when Jira requires token-based authentication. A token can also grant access through your account permissions, so creating one without understanding its scope or storage creates avoidable risk. But here's the truth: you can create a Jira API token in a few minutes, then test it with a simple request. Follow these five steps to make the right kind of token, connect it to Jira, and keep it protected. I’ll also show you what to check if a request returns an error.
How to Create a Jira API Token in 5 Steps
To create a Jira API token, sign in to your Atlassian account, open API token settings, create a token, copy it securely, and authenticate with your Atlassian email address. Your account permissions still determine what the token can access.
-

1. Sign in to your Atlassian account
Open the Atlassian account management page and sign in with the account you use for Jira. The token belongs to that account, so make sure it is the right one before continuing.
If you have separate accounts for work and personal projects, check the account email carefully. A token created under the wrong account won’t grant access to the Jira site you intend to use.
-
2. Open the API token settings
Go to your account’s Security settings and find API tokens. You can also navigate directly to id.atlassian.com/manage-profile/security/api-tokens after signing in.
Choose the option to create an API token. Atlassian may show options for a regular token or a token with scopes. The options you see can depend on your account and the integration you’re setting up.
-
3. Name the token and set its access
Give the token a clear name that identifies its purpose, such as Jira reporting script or CI issue updates. A useful label makes it easier to recognize later when you review or revoke tokens.
If Atlassian offers scope settings, grant only the permissions the integration needs. For example, a reporting task that reads issues shouldn’t receive write access unless it must change Jira content.
Choose an expiry period that fits the task and your organization’s security policy. A short-lived token is preferable for a temporary test; a regularly used integration needs a planned renewal process.
-
4. Create the token and copy it immediately
Confirm the settings and create the token. Copy it when Atlassian displays it, then place it in an approved secrets manager or another secure credential store.
You may not be able to view the full token again. If you lose it, revoke it and create a replacement. Don’t paste it into a public chat, commit it to code, or include it in a screenshot.
-
5. Use the token to authenticate and test Jira access
For a basic Jira Cloud REST API request, use your Atlassian account email as the username and the token as the password. This example checks the identity associated with the credentials:
curl --user "you@example.com:YOUR_API_TOKEN" \
--header "Accept: application/json" \
"https://your-domain.atlassian.net/rest/api/3/myself"
Replace the email, token, and Jira site address with your own values. A successful response confirms that authentication worked, though the token still only has the permissions available to its account.
Scoped tokens may require the Atlassian API gateway and a matching request path instead of your site’s direct address. Follow the endpoint format Atlassian specifies for the token type and scopes you selected.
What a Jira API Token Does—and What It Doesn’t
A Jira API token is a credential that lets an application authenticate to Jira Cloud through your Atlassian account. It is commonly used by scripts, integrations, and command-line requests that need to interact with Jira’s REST API.
Here's why: the token replaces your account password for API authentication, reducing the need to expose your password to an integration. It does not create a separate Jira identity or automatically grant broader access.
The token acts with the permissions associated with your Atlassian account, subject to the token’s scopes when applicable. If your account cannot view a project, a token created under that account generally cannot view it either.
An API token is also different from an OAuth app connection. Tokens are convenient for a personal script or a controlled integration, while OAuth is often more suitable when an app needs delegated access across multiple accounts.
Choose the Right Token Type for Your Integration
Before you connect an integration, check whether it supports the token type you plan to create. Older integrations may expect a standard API token, while newer setups may support scoped tokens with selected permissions.
For example, a small Python script that checks your own Jira issues may use a standard token. An integration requesting scoped access may need a token configured for specific Jira permissions and Atlassian’s gateway URL.
| Integration situation |
What to check |
| Personal script for one Jira account |
Confirm the script supports Atlassian email and API token authentication. |
| Integration that requests scopes |
Choose only the required scopes and use the endpoint format specified for scoped tokens. |
| Shared or business-critical connection |
Check your organization’s policies for service accounts, credential storage, and token rotation. |
| Third-party connector |
Verify its current Jira Cloud authentication instructions before creating a token. |
Let me explain: the same credential can fail when it is paired with the wrong endpoint or authentication format. Confirm both before troubleshooting Jira permissions.
Protect and Maintain Your API Token
Treat a token like a password, even if you’ve limited its scopes. Anyone who obtains it may be able to act through the associated account within the access available to that token.
- Store it securely. Use a secrets manager or your organization’s approved credential storage instead of placing it directly in code.
- Keep it out of logs. Avoid printing request headers or credentials when debugging an integration.
- Limit access. Give the token only the scopes and account permissions needed for its task.
- Set a renewal reminder. Replace expiring tokens before a scheduled job or integration stops working.
- Revoke unused credentials. Remove tokens when a test ends, an integration is retired, or a token may have been exposed.
A practical example: if a scheduled report runs every Monday, test its replacement token before the current one expires. That gives you time to update the credential safely and confirm the next run.
Fix Common Jira API Token Errors
401 Unauthorized: Check the email address, token value, and authentication format. Make sure you copied the complete token and haven’t accidentally included spaces or quotation marks in the credential.
403 Forbidden: Authentication may have succeeded, but the account or token lacks permission for the requested action. Check project access, Jira permissions, and any scopes required by a scoped token.
404 Not Found: Verify the Jira site address and REST API path. If you use a scoped token, confirm that the request uses the appropriate Atlassian gateway endpoint.
Token stopped working: Check its expiry and whether an administrator or account owner revoked it. Create a replacement, update the integration’s stored credential, and test the connection again.
You might be wondering: how can you tell whether the problem is the token or the request? Test a simple identity endpoint first. If that works, check the path, project permissions, and requested operation next.
Jira Project Management Alternative: ONES.com
ONES.com brings project management and knowledge management together in one platform. ONES Project is its project management product and a Jira alternative; ONES Wiki is its knowledge base product and a Confluence alternative. They are sold separately.

This is relevant if you’re reviewing how your team manages projects alongside integrations and access controls. ONES Project offers Jira-compatible workflows, but it is a separate platform; don’t assume a Jira API token works with it.
Core capabilities
- Jira workflows need a familiar transition. ONES Project supports Jira-compatible workflows, helping teams adapt existing processes with less disruption.
- Teams need visibility into delivery. Built-in reporting gives project leads a way to track progress without relying on a collection of add-ons.
- Different projects need different processes. Custom workflows and fields let teams represent the information and approval steps their work requires.
- Sprint planning needs structure. Sprint management supports teams organizing work into planned development cycles.
- Repeated actions take time. Automation can handle supported routine workflow tasks, reducing manual effort.
- Plugin dependence can complicate upkeep. Native capabilities can reduce the need for multiple plugins for common project management needs.
- Deployment requirements vary. ONES.com is available as Cloud, On-Premise, Private Cloud, and Air-gapped deployments.
- Self-hosting shouldn’t mean losing features. ONES.com offers full feature parity between its cloud and self-hosted versions.
Where it may fit
A software team moving from Jira can assess ONES Project when it wants Jira-compatible workflows, built-in reporting, and sprint management in a project management platform. The team can map its current workflow and check whether the required permissions and integrations are supported.
A company with restricted network requirements can review On-Premise, Private Cloud, or Air-gapped deployment options. Its administrators can compare deployment requirements while project teams evaluate the workflow and reporting features they need.
ONES.com also includes ONES Assistant, its AI-powered assistant. The platform is free for up to 30 seats. Review the specific products, deployment, and capabilities that fit your team before making a change.
Common Challenges When Creating a Token
- You can’t find the token settings. Confirm that you’re signed in to the right Atlassian account, then open its Security settings and select API tokens.
- You didn’t save the token when it appeared. Revoke it if needed and create a new one. Store the replacement securely at creation time.
- The token authenticates but can’t access a project. Check the account’s Jira permissions and any token scopes. Authentication alone doesn’t grant project access.
- An integration rejects the token. Compare its current instructions with your token type, authentication format, and endpoint. Scoped tokens may use a different URL pattern.
- A scheduled task fails after working previously. Check token expiry, revocation, and credential updates. Test a replacement before removing the existing working connection.
FAQs About Jira API Tokens
Is a Jira API token the same as my Atlassian password?
No. A Jira API token is a separate credential for API authentication. You use it with your Atlassian email address where the integration expects token-based authentication. Keep it private like a password, and don’t use your account password in scripts or integrations that support API tokens.
Can I see an API token again after creating it?
Atlassian may show the token only when you create it, so copy and store it securely at that point. If you can no longer access the value, revoke the token and create a replacement. Update the integration that uses it, then test the connection to confirm the new credential works.
Why does my Jira API token return a 401 error?
A 401 error usually points to an authentication problem. Check that you’re using the correct Atlassian email, the full token, and the authentication format expected by the integration. Also confirm that the token hasn’t expired or been revoked. For scoped tokens, check that you’re using the correct endpoint format.
Do Jira API tokens have an expiry date?
Token settings can include an expiry period, and the available options may vary. Check the expiry shown when creating the token and follow your organization’s policy. If an integration depends on a token, plan and test its replacement before the current credential expires.
Should I use a standard or scoped API token?
Choose the type your integration supports and grant only the access it needs. A standard token may suit a simple personal script, while a scoped token can offer more specific access controls when the integration supports it. Check Atlassian’s current instructions for the relevant endpoint and authentication method before choosing.
Conclusion
Creating a Jira API token takes five steps: sign in, open token settings, configure access, copy the token securely, and test a Jira request. The token uses your account’s permissions, so check access and scopes as well as authentication.
But here's the truth: most avoidable problems come from a lost or expired token, a mismatched endpoint, or permissions that don’t fit the request. Store the credential securely, plan renewal, and revoke tokens you no longer need. With those habits in place, you can connect Jira integrations more reliably and keep your account protected.