Get your Anthropic API key

A plain-English, no-jargon setup — about 5 minutes, one time. No technical background needed.

Spec2Tickets uses Anthropic's Claude AI to turn your Confluence pages into Jira backlogs. To do that, it connects to your own Anthropic account using a short text “key”. You create that key once, paste it into Spec2Tickets, and you're done — the AI then runs under your own account.

Why your own key? It keeps you in control: your content is processed under your Anthropic agreement, and you pay Anthropic directly for AI usage (a few cents per breakdown) with no markup from us. We never see or store your key in readable form.

Not the technical type? That's fine. Every step below is just clicking and copying — but one step needs a payment method (a company card or credits) on the Anthropic account. If someone on your team handles tool subscriptions or billing, this is a nice 5 minutes to do together. Send them this page.

What you'll need

An email address	To create the Anthropic account (or use one your team already has).
A payment method	A credit card or pre-purchased credits on the Anthropic account. A small amount (≈ $5–10) is plenty to start.
~5 minutes	One time. After this, Spec2Tickets just works.

The 4 steps

Create your Anthropic account

Go to console.anthropic.com and sign up (or sign in if your team already has an account). Confirm your email if asked. This is Anthropic's “Console” — the dashboard for the company that makes Claude.

Add billing or credits

In the Console, open Settings → Billing (or “Plans & Billing”) and add a payment method, or buy a small amount of credits. You don't pre-pay for Spec2Tickets here — you're just enabling the Anthropic account to run AI when you use it.

This is the step people skip — don't. Without billing or credits set up, your key will exist but won't work, and Spec2Tickets will show a “billing not enabled” message when you try to generate. Adding a card (or ~$5 of credits) now avoids that.

Create the key and copy it

Open Settings → API Keys → Create Key. Give it a name you'll recognise later, like Spec2Tickets, and create it. Anthropic shows the key — a long string that starts with sk-ant-api03-….

Copy it right away. Anthropic shows the full key only once. Copy it to your clipboard now (you'll paste it in the next step). If you lose it, no problem — just create another one.

Paste it into Spec2Tickets

In Confluence, open Apps → Spec2Tickets, then click Settings (top-right of the app). Paste your key into the Anthropic API Key field, set your default Jira project key, and click Test & Save. A green confirmation means you're connected.

That's it. Your key is stored in Atlassian's encrypted Forge secret storage — it's never shown back in the app and never sent to Spec2Tickets' own servers (we don't run any). You're ready to generate your first breakdown.

What does it cost?

You're billed by Anthropic for the AI usage, directly, with no markup from us. In practice:

A typical breakdown costs a few US cents.
Test-case generation (an Advanced-edition feature) costs more — usually under a dollar per run.
Spec2Tickets always shows you an estimate before you run a paid action, and the exact amount after — so there are no surprises.

The Spec2Tickets subscription itself (from the Atlassian Marketplace) is separate and covers the app; see Pricing.

If something goes wrong

“API key not configured”	The key isn't saved yet — repeat Step 4 in the app's Settings.
A billing / credits error	The key is valid but the Anthropic account has no active billing — go back to Step 2 in the Console.
“Invalid / rejected key”	The key was mistyped or revoked — create a fresh one (Step 3) and paste it again.
Lost the key	You can't view an old key again, but you can create a new one any time in the Console (Step 3).

Still stuck? Email support@spec2jira.com — we're happy to walk you through it.

Open the Anthropic Console →