My API Token not working

[Chou_ Peter]

My API token has stopped working. It was working a few days ago, but I've been getting this error:

message: "Unable to list entities."

stacktrace: "com.google.cloud.connectors.runtime.v1.errors.ConnectorException: Unable to list entities. metadata { key: "cause" value: "Unable to retrieve columns for table [Issue]."

I've been testing with Google's ADK agent, and I don't know if the amount of requests to the Jira API has raised a flag with Jira and now my token is being blocked.

[Matteo Vecchiato]

Hi @Chou_ Peter ,

Welcome to Atlassian community.

is there the possibility to have which api is called and the json response?

As far as I know, there isn't a limit in the api calls. You can check your token status in two way:

• In your personal account setting security: https://id.atlassian.com/manage-profile/security/api-tokens 
• By a Org admin in the Admin section -> security -> User api token.

Kind regards

[Chou_ Peter]

Hi @Matteo Vecchiato , Thx for replying.  My token appears to be valid. Coincidentally, it started working after I posted this message. But it appears to be inconsistent. I don't if the issue lies with the Jira API or Google's ADK Agent.

On another matter, if I want to test the Jira API using curl, where can I get my Bearer token. The doc says to go to my profile and there should a link to my Personal Access Token but I can't find the link. Do I need a specific role to see it?

Thanks,

Peter

[Matteo Vecchiato]

Hi @Chou_ Peter

you should click on your user icon (on top right), choose Account settings and then Security -> Api tokens

You can access to a previous generated api tokens, they are showed only one time when generated; but you can create a new one.

If you don't see this section, it means that your organization admin has disabled the option to generate api tokens.

Kind regards

[Chou_ Peter]

Hi @Matteo Vecchiato Actually I was able to use:

curl -u <email@address.com>:<API TOKEN> <REST URL>

which works.

Before, I tried to use :

curl --request GET \

  --url '<REST URL>' \

  --header 'Authorization: Bearer <API TOKEN>' \

  --header 'Accept: application/json'

which didn't work. This one requires a personal access token which I didn't have. My API Token didn't work here.

Thanks,

Peter