Jira API Token Creation: 6 Steps for a Secure Setup Guide
Searching for “jira create api token” help? Follow six steps to set up and secure your Jira Cloud token. Read now to protect your access.
A Jira API token can unlock useful automation, but a token that leaks may let someone act through your Atlassian account. That risk grows when credentials end up in scripts, shared chats, or forgotten integrations.
Creating one takes only a few minutes. Keeping it secure requires a little more care: you need the right token type, a safe place to store it, and a plan to revoke it.
Here’s the practical route. I’ll walk you through six steps to create a Jira Cloud API token, connect it safely, and check its access. You’ll also learn what changes if your team uses Jira Data Center.
How to Create a Jira API Token in 6 Steps
For Jira Cloud, create an API token in your Atlassian account’s security settings, store it securely, and use it instead of your account password for API authentication. The steps below cover the process from creation through ongoing protection.

1. Confirm that you use Jira Cloud
These steps apply to Jira Cloud accounts, which usually have an address like your-team.atlassian.net. Jira Data Center uses a different personal access token process, described later in this guide.
Check your Jira address before creating credentials. That small check helps you avoid generating a token that your server or integration cannot use.
2. Open your Atlassian account security settings
Sign in to the Atlassian account connected to Jira. Go to id.atlassian.com/manage-profile/security/api-tokens, or open your profile settings and select the API token section.
If you have multiple Atlassian accounts, confirm the account email before continuing. The token will authenticate as that account, so its Jira permissions matter.
3. Create and label the token
Select the option to create an API token. Atlassian may show a standard token option or an option for a scoped token, depending on your account and current settings.
Give the token a clear label, such as inventory-sync-prod or qa-dashboard-staging. A useful name helps you identify its owner and purpose during a security review.
If the screen offers an expiration date, choose one that fits the integration’s expected lifetime. If scoped tokens are available, grant only the permissions the task needs.
4. Copy it once and store it safely
Copy the token when Atlassian displays it. You may not be able to reveal it again after closing the creation screen, so save it directly into an approved secrets manager.
Do not paste it into a chat, a ticket, a browser address bar, or a script committed to version control. If a teammate needs access, use your organization’s credential-sharing process rather than sending the token casually.
5. Authenticate with your email and token
For Jira Cloud Basic authentication, use your Atlassian account email as the username and the API token as the password. Do not use your regular Atlassian password in an API request.
For example, this request checks the identity associated with your credentials. Replace the example host, email, and token with your own values.
curl --user 'you@example.com:YOUR_API_TOKEN' \
--header 'Accept: application/json' \
'https://your-team.atlassian.net/rest/api/3/myself'
Keep the real token out of terminal history and shared command logs. For production integrations, retrieve it through a secrets manager or a protected environment variable.
6. Test, review, and revoke when needed
Run a small test against the intended Jira project or endpoint. Confirm that the integration can complete its task without receiving broader access than it needs.
Review active tokens periodically. Revoke credentials tied to retired integrations, former team members, or unfamiliar labels. Create a replacement token before revocation only when the service needs uninterrupted access.
Choose the Right Token and Access Level
Token type matters because Jira Cloud and Jira Data Center handle API credentials differently. Here’s why: using the wrong credential can make a valid request fail, even when the account and password are correct.
Jira Cloud API tokens are linked to an Atlassian account. Requests made with a standard token generally receive that account’s existing permissions, so the token itself does not automatically make access more limited.
When scoped tokens are available, choose only the permissions needed for the integration. For example, a reporting service that reads issue details should not receive write access unless it truly updates Jira.
Cloud tokens and Data Center personal access tokens
Jira Cloud uses API tokens created through Atlassian account security settings. Jira Data Center commonly uses personal access tokens managed within the Jira instance, with availability and controls depending on the administrator’s configuration.
Ask your Jira administrator which edition your organization runs if you are unsure. An address on a company network or a custom domain alone may not make the distinction clear.
Use a dedicated account when appropriate
For a long-running integration, a dedicated service account can make ownership and access reviews easier. Give it only the Jira project permissions required for its job, and assign a clear owner who will monitor it.
For example, a release-reporting integration may only need to read selected project issues. A service account with project-specific read access is easier to review than a personal account with broad administrative privileges.
Protect the Token Throughout Its Lifecycle
A token is a credential, so treat it with the same care as a password. The best part? A few repeatable habits can prevent many common leaks without slowing down everyday work.
Store tokens in a managed secrets service, limit who can retrieve them, and avoid embedding secrets in application code. When a script runs in a CI/CD environment, use that environment’s protected secret settings.
Set a rotation and revocation plan
Record the token’s purpose, owner, creation date, and renewal date in an approved access register. Keep the record free of the token itself.
When rotating, create the replacement, update the integration, test it, and then revoke the old credential. This sequence helps prevent unnecessary service interruptions.
Watch for accidental exposure
Check command history, build logs, error reports, and code review changes if you suspect a token leaked. Revoke a compromised token promptly, then create a replacement and investigate where it appeared.
Never try to “hide” a leaked token by editing a message or removing a visible code snippet alone. Once exposed, assume someone could have copied it and replace it.
Test Requests and Troubleshoot Authentication
Start with a simple identity request, then test the specific Jira action your integration needs. This separates authentication problems from endpoint, project permission, or request-format problems.
If the identity request fails, verify the account email, token value, and Jira Cloud site address. Also check that your request uses HTTPS and sends credentials through the expected authentication method.
Common response clues
- 401 Unauthorized: Check for a mistyped email, expired or revoked token, or incorrect authentication format.
- 403 Forbidden: Authentication may have succeeded, but the account may not have permission for the requested project or action.
- 404 Not Found: Verify the site address, API path, and issue or project identifier. Some endpoints may also hide restricted resources.
Use the least sensitive test available. Avoid printing credentials in debug output, and remove temporary diagnostic logging once the issue is resolved.
Jira API Token Setup: A Project Management Alternative with ONES.com
ONES.com is a unified project management and knowledge management platform. ONES Project handles project management and is a Jira alternative; ONES Wiki provides knowledge management as a Confluence alternative. They are sold separately.

ONES.com does not create or manage Jira API tokens. If you are reviewing tokens because Jira-specific integrations have become difficult to maintain, you can also assess whether some project work belongs in a different platform.
Value Proposition
ONES Project brings planning, execution, and reporting into a project management environment with Jira-compatible workflows. Teams can evaluate it as a way to reduce reliance on add-on plugins for supported project processes.
Core Capabilities
- Scattered project tracking → Jira-compatible workflows → Teams can use familiar issue and project patterns while assessing a Jira alternative.
- Extra plugins for common reporting → Built-in reporting → Project leads can review progress without depending on a separate reporting add-on for supported views.
- Rigid work processes → Custom workflows → Teams can shape task movement around their approval or delivery steps.
- Fields that miss team context → Custom fields → Teams can capture details relevant to their work without relying on the same fields for every project.
- Sprint planning spread across processes → Sprint management → Agile teams can plan and track sprint work within the project platform.
- Repeated manual task handling → Automation → Teams can automate supported workflow actions and reduce routine administration.
- Deployment constraints → Cloud, On-Premise, Private Cloud, or Air-gapped deployment → Organizations can select an environment that matches their infrastructure needs.
- Separate PM and knowledge needs → ONES Project and ONES Wiki options → Teams can select the products relevant to them, with each sold separately.
ONES.com offers a free plan for up to 30 seats. Its cloud and self-hosted versions have feature parity, allowing teams to evaluate deployment requirements alongside project workflows.
Application Scenarios
Scenario 1: A team reviewing a Jira integration backlog. A team that maintains several scripts and plugins can map each process, identify which work depends on Jira APIs, and assess whether ONES Project’s built-in capabilities fit selected workflows. Any external integration still needs its own credential review.
Scenario 2: An organization with restricted network requirements. A company that cannot use a public cloud service can evaluate ONES Project’s On-Premise, Private Cloud, or Air-gapped deployment options. Its administrators can consider project workflows and environment requirements together.
Common Challenges When Creating Jira Tokens
- The token disappears after creation. The token may only be shown once. If you did not store it securely, revoke it and create a replacement rather than trying to recover it.
- An integration still receives an authentication error. Confirm the correct account email, token value, site address, and authentication format. Then test a simple identity endpoint.
- The request authenticates but cannot access an issue. Check the account’s Jira permissions and project access. A token does not grant privileges beyond the account’s permissions.
- A service breaks during token rotation. Update the service with the replacement token, test its operation, and revoke the old token after the new one works.
- No one knows which integration owns a token. Use descriptive labels and maintain an owner and purpose for each credential. Revoke unidentified or abandoned tokens after confirming their use.
Frequently Asked Questions
Is a Jira API token the same as a password?
No. A Jira Cloud API token is a separate credential used for API authentication, while your account password is used to sign in through supported account methods. For Basic authentication, pair your Atlassian account email with the token. Keep the token private, and do not use your regular account password in API requests.
Can I create a Jira API token for another person?
API tokens are associated with the Atlassian account that creates them. A safer approach is to have the integration owner or an approved service account create its own token. That keeps ownership clear and avoids sharing a personal credential between teammates.
What should I do if I accidentally expose my token?
Revoke the exposed token in your Atlassian account security settings as soon as possible. Create a replacement, update the integration through a secure channel, and check relevant logs or messages to understand where the old token appeared. Do not assume deleting the visible text removes copies already made.
Can I use an API token with Jira Data Center?
Jira Data Center commonly uses personal access tokens rather than Atlassian Cloud API tokens. Availability and administration depend on the instance configuration. Ask your Jira administrator for the approved method and the permissions your integration should receive before creating a credential.
Conclusion
Creating a Jira Cloud API token is straightforward: confirm your Jira edition, create and label the token, store it securely, and test the intended request. Afterward, review ownership and access, rotate credentials carefully, and revoke anything you no longer need.
An API token can simplify an integration, but an exposed credential can put your account’s Jira access at risk. A clear lifecycle turns the setup into a manageable security practice. If recurring Jira integrations are driving a broader workflow review, evaluate the processes first and consider whether a Jira alternative such as ONES Project fits selected needs.