Excel Power Query Jira API Key Name: What to Enter

How-to basics · Updated November 19, 2026

For Jira Cloud, the “API key name” box in Power Query is not the name of your Jira API token: it is the query-string parameter name an API expects for a key. Jira Cloud API tokens are normally used with Basic authentication, so entering a name such as Authorization in that box is not the right way to authenticate. Use your Atlassian account email and API token in an HTTP Authorization header instead.

What Power Query means by API key name

Power Query’s Web API authentication option is designed for services that accept an API key as a URL query parameter. The API documentation tells you the required parameter name; common examples on other services include api_key or key. The name is not a label you invent for your secret, nor is it necessarily a username. Power Query sends the key under that parameter in the request URL.

That distinction matters because a request with a key in the query string is different from one with an HTTP header. If you type Authorization as the API key name, Power Query may treat it as a URL parameter name; it will not automatically construct Jira’s Basic authentication header. For Jira Cloud, follow Atlassian’s authentication method rather than guessing at a parameter name.

How Jira Cloud API token authentication works

For Jira Cloud REST API access, Atlassian’s standard Basic authentication pattern combines the Atlassian account email address and an API token, then encodes that pair as Base64. The encoded value goes in an HTTP header in this form: Authorization: Basic [encoded credentials]. The token is not the same as your Atlassian password, and Base64 encoding is not encryption; anyone who obtains the encoded string can decode it.

Create an API token through your Atlassian account’s security settings, and use the email address associated with that account. Give a token only the access it needs where token controls permit, and revoke it if it is exposed or no longer required. Jira permissions still apply: successful authentication does not grant access to projects or issues the account cannot view.

Jira Data Center and older Jira Server installations are different environments. Their authentication options depend on the product version and administrator configuration; some support personal access tokens sent as Bearer tokens, while others use different arrangements. Check the REST API documentation for the exact Jira instance before copying a Cloud example.

Connect from Excel Power Query with an Authorization header

In Excel for Microsoft 365 on Windows, open Data > Get Data > From Other Sources > Blank Query. In the Power Query Editor, choose Home > Advanced Editor. The following example calls Jira Cloud’s current-user endpoint to check that authentication works. Replace the example host and placeholders; do not leave the placeholder values in place.

let
    email = "your-atlassian-email@example.com",
    apiToken = "paste-your-api-token-here",
    auth = "Basic " & Binary.ToText(
        Text.ToBinary(email & ":" & apiToken),
        BinaryEncoding.Base64
    ),
    Source = Json.Document(
        Web.Contents(
            "https://your-site.atlassian.net",
            [
                RelativePath = "rest/api/3/myself",
                Headers = [Authorization = auth, Accept = "application/json"]
            ]
        )
    )
in
    Source

Choose Done, then load or inspect the result. A successful call returns account details as JSON. The site address should be the base address of your Jira Cloud site, such as https://example.atlassian.net, not a project page or a URL copied from a browser search. The endpoint in the example is a useful authentication check; it does not retrieve issues.

For this custom-header pattern, Power Query’s saved permission for the site generally needs to use Anonymous authentication, because the query itself supplies the Authorization header. In Excel, review Data > Get Data > Data Source Settings, select the Jira site, and edit its permissions if required. Do not select Web API and enter a Jira token as though Jira expects it as a query parameter.

Requesting issues and handling Jira responses

Once the connection test succeeds, change the relative path and add the parameters required by the Jira REST endpoint you intend to use. For example, an issue-search request needs a JQL expression and commonly uses a request limit. The exact search endpoint and paging method can change, so consult the REST API documentation for your Jira Cloud version rather than assuming an old example remains current. Jira Cloud’s newer search APIs may use a page token, while older search patterns use an offset.

Power Query initially displays a JSON response as records, lists, and nested values. Use the expand buttons in the column headers to turn fields such as issue key, summary, status, and project into table columns. Expand only the fields you need: issue records can contain nested objects and large amounts of data, and expanding everything can make refreshes slower and the resulting table harder to maintain.

Search results are usually paginated. A request that returns the first page is not proof that it returned every matching issue. Build pagination according to the endpoint’s response fields, and check whether it provides a next-page token, a start offset, a total count, or another continuation mechanism. Also consider Jira’s result limits and rate limits when planning a refresh that may fetch many records.

Keeping the token safe

The sample makes the authentication method visible, but it also illustrates an important security trade-off: putting a token directly in M code can expose it to people who can inspect the query or workbook. A workbook stored in a shared folder, emailed to others, or published for others to refresh should not be treated as a secure secret store. Base64 only changes the representation of the credentials.

  • Use a dedicated account or token with only the Jira access needed for the refresh.
  • Do not publish a workbook containing a live token to a location where unintended readers can inspect its queries.
  • Revoke and replace a token if it appears in a shared file, screenshot, log, or public repository.
  • For centrally managed or shared production refreshes, consider an approved connector or integration that handles credentials separately from workbook code.

Power Query’s Web API credential option can store a key as a data-source credential, but it is intended for APIs that accept the key in the documented query-string form. It is not a general-purpose way to store a Jira token and automatically convert it into the required Basic header. If you need stronger credential management, ask your Microsoft 365 or Jira administrator about the organization’s supported refresh and connector options.

Common errors and what they usually mean

  • 401 Unauthorized: Check the account email, token, encoding, and header format. Confirm that the token is active and belongs to the account used in the request.
  • 403 Forbidden: The account may have authenticated successfully but lack permission for the requested Jira resource. Check project and issue permissions as well as any administrator restrictions.
  • 404 Not Found: Check the site hostname, REST path, API version, and whether the endpoint is available for that Jira product. A browser page URL is not necessarily a REST API URL.
  • Power Query credential or privacy prompt: Inspect Data Source Settings for the site and remove conflicting saved permissions if appropriate. For a request whose M code sets the Authorization header, use the authentication setting required by that pattern.
  • Only some issues appear: Check paging and the endpoint’s maximum page size. Jira may return a valid first page without returning the full result set.

Do not troubleshoot by placing a token in a guessed URL parameter. Besides being the wrong authentication method for the standard Jira Cloud pattern, query-string secrets can be exposed in URLs, browser history, logs, and diagnostics.

Excel, Power BI, and other connection options

Excel Power Query and Power BI use the same M language and share many concepts for web requests, but their credential interfaces, refresh environments, and administrative controls are not identical. A query that refreshes in desktop Excel may need separate configuration if it is moved to a managed Power BI service or another hosted refresh environment. Confirm how credentials will be supplied and who can refresh before distributing a report.

On Excel for Mac, Power Query availability and the exact supported data-source and credential experiences can differ by Microsoft 365 build. If the relevant Web or query-editing options are missing, check the current Excel for Mac feature support and your organization’s update channel. The M approach is not a replacement for a platform’s credential policy, and a Windows walkthrough should not be assumed to match every Mac dialog.

For recurring team reporting, alternatives include an organization-approved Jira connector, a managed ETL or integration service, or a scheduled export into a governed data source. A connector may simplify authentication and paging, but verify its permissions, maintenance, data handling, and licensing before relying on it. Manual CSV exports can be adequate for occasional small extracts, but they are less suitable when the report must refresh automatically or preserve a repeatable query.

Frequently Asked Questions

What should I enter for Jira’s API key name in Excel?
For Jira Cloud Basic authentication, do not enter a key name in Power Query’s Web API key-name field. That field is for APIs that require a key as a URL parameter; Jira Cloud’s standard API-token method uses an Authorization header.

Is the Jira API key name “Authorization”?
No. Authorization is the HTTP header name for the Basic authentication value. It is not the query-parameter name to enter in Power Query’s Web API credential prompt.

Can I use my Jira password instead of an API token?
For Jira Cloud, use an API token with the account email in the Basic authentication pattern, not your normal Atlassian password. For self-managed Jira, follow the authentication rules configured for that specific instance.

Why does Power Query ask me to sign in after I add the header?
Power Query saves credentials by data-source address. The saved authentication method may conflict with a custom Authorization header. Review the Jira site under Data > Get Data > Data Source Settings and set permissions to match the header-based request.

Is a Base64-encoded Jira token secure?
No. Base64 is encoding, not encryption. Treat the complete Authorization value as a password-equivalent secret, restrict access to the workbook and query, and avoid embedding a live token in files shared with people who should not use it.

Bottom line

The phrase “API key name” refers to a URL parameter name required by some APIs; it is not the name of a Jira token. For Jira Cloud in Excel Power Query, use the account email and API token to create the documented Basic Authorization header, set the data-source credential appropriately for a custom header, and protect the token as a secret. Check the documentation for your Jira product and endpoint before building a larger query, especially when permissions, pagination, or automated refresh are involved.

Related

Try it: the Date Difference Calculator: days, months, years and weekdays between two dates, with the DATEDIF formulas.

More in How-to basics

Sources: Function behaviour and menu paths: Microsoft Support documentation for Excel. Method & sources

Spotted an error in this guide? Let us know.