Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Not able to create agent using Claude agent for JIRA

Ankush Katiyar
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 13, 2026

Hello,

I m setting up claude agent for jira, https://support.atlassian.com/jira-software-cloud/docs/set-up-claude-agent-for-jira/

But when i enter both API keys( claude and github ) i got error Failed to create agent: 400
I dont see exact root cause for this error and what about next steps

Screenshot 2026-08-14 at 12.15.35 PM.png 

2 answers

0 votes
Sami Shaik
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
August 14, 2026

Hello @Ankush Katiyar , welcome! @Gor Greyan DevTools route is the right way to see the real error, and before you go there, three causes fix most 400s on this exact screen

1. The Claude key must be an API key, not a Claude subscription. It comes from the Anthropic Console, and the workspace behind it needs active billing or credits. A Claude Pro or Team login is a different thing entirely and will not validate, this is the single most common trip-up.

2. Re-check the GitHub token type and scopes against the doc. Classic and fine-grained personal access tokens behave differently, and a token missing the repository scopes the setup doc lists fails exactly like this at creation time.

3. Re-paste both keys watching for whitespace. A trailing space or newline from a copy is invisible in the field and produces a clean 400.

If all three check out, then Gor's path: the Network tab's response body usually names the failing field, and if it is a bare 400 with nothing more, that plus a HAR file to Atlassian Support is the right escalation, this feature is new enough that rollout gating is also possible, and the response body will say so.

0 votes
Gor Greyan
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
August 14, 2026

Hi @Ankush Katiyar

Welcome to the Atlassian Community!

I would check the browser Developer Tools → Network while clicking Create agent and inspect the failed request/response. It may contain a more specific validation error than the UI displays.

If it only returns a generic 400, I think the best option is to raise this with Atlassian Support and provide the screenshot, HAR file, approximate timestamp, and the failed request details. They should be able to trace the backend failure.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events