The authorization header are not working for Jira API Token

[Suraj Navalagi]

Jira API tokens are used as authorization headers in Splunk On‑Call along with the Jira webhook. When an incident is created in Splunk On‑Call, it automatically triggers the creation of a Jira ticket using these credentials.

While reviewing the Splunk logs for the triggered incidents, we observed HTTP 401 (Unauthorized) errors. This indicates that the authorization request to Jira is being rejected.

Could you please check and confirm whether the Jira API token being used is still valid and has not expired, been revoked, or had its permissions changed? Additionally, please verify that the token is correctly configured in the integration settings.

[Chethan GR]

Hi @Suraj Navalagi

Please check if the API token used is still valid and if not then please try with a new token.

[Suraj Navalagi]

Yes, the Jira API Token used is valid one. They are using the fresh API token.

[Suraj Navalagi]

Hello @Chethan GR  the API Token are valid do you have any other solution on this?

[Arkadiusz Wroblewski]

Hello @Suraj Navalagi 

A 401 error is strictly about authentication, so it means Jira isn't accepting your credentials at all. Since we're right in the middle of the May 2026 token expiry window, it's very likely your current API token has simply timed out. I’d start by rotating that token at id.atlassian.com and plugging the new one into Splunk.

Make sure Splunk is still sending it as a Basic Auth header (the base64-encoded version of your email:token). If you happened to use a newer "scoped" token, that might be the culprit too, as those don't always play nice with standard site URLs. Try a classic token first.

[Suraj Navalagi]

Hello @Arkadiusz Wroblewski The token was expired on 20th March so we created a new token  when we used the Basic auth method in Splunk On-call we are getting 401 error from our Splunk logs. kindly provide your inputs on this.