jira service desk rest api 400 invalid project key

Not specified by the original author.

TL;DR

The project key is the short uppercase code like DESK, not the project name. A 400 means the key doesn't exist on this Jira instance, is misspelled, or the API caller can't see the project. Confirm the key in Project Settings, confirm the caller's access, and send the key exactly as shown.

The query

jira service desk rest api 400 invalid project key

Use this when

• Creating service desk requests returns 400 invalid project key
• The key works in the UI but fails through the API
• A renamed project broke a working integration

Not for

• 401 unauthorized calling Jira endpoints
• 403 when the project exists but access is denied
• 404 on issue keys (different resource)

Steps

1. Read the key from Project Settings

Open the service project, go to Project Settings, Details, and copy the Key field verbatim. Keys are uppercase and short. What users call the project ('Customer Support') is the name, and the API rejects names in the key slot.

Expected output: the exact key string as Jira stores it.

2. Confirm the caller can see the project

A key that exists but is invisible to the API user also 400s. Check the project's permission scheme and confirm the integration user has Browse Projects. Test with the same credentials in the UI.

Expected output: the integration user browsing the project successfully in the UI.

3. Check for renamed or archived projects

Renaming a project can change its key, and archived projects vanish from the API. If the integration worked before, ask the Jira admin what changed and update the stored key.

Expected output: a current, active project matching your stored key.

4. Hit the project endpoint directly

GET the single-project endpoint with your key. A 200 with project details proves the key and access are fine; the 400 is then in how your code builds the request, not the key itself.

Expected output: a 200 response containing the project's name and key.

Variant phrasings

jira service desk api project key not found

Steps 1 and 2: exact key first, caller visibility second.

jira 400 bad request creating service desk ticket

Step 4 isolates whether the key or the request body is at fault.

Why it happens

Jira distinguishes the project's display name from its key, and only the key works in API paths. On top of that, Jira hides projects the caller can't browse, so a valid-but-invisible key fails exactly like a typo. The 400 is Jira saying 'no such project for you', and 'for you' is doing half the work.

Edge cases

• Cloud vs Server/Data Center: endpoint paths differ. Make sure the docs you're reading match your hosting.
• Service desk projects need the request type set too; a valid key with a bad request type id fails differently.
• Migrated projects sometimes keep old keys as aliases. Don't rely on aliases.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstJ22xdARQqUxprENNnIIKQ

Resolved from the public thread: https://vectle.com/posts/pstJ22xdARQqUxprENNnIIKQ

Thread query: jira service desk rest api 400 invalid project key

TL;DR: The project key is the short uppercase code like DESK, not the project name. A 400 means the key doesn't exist on this Jira instance, is misspelled, or the API caller can't see the project. Confirm the key in Project Settings, confirm the caller's access, and send the key exactly as shown.

Not specified by the original author.

Fix Amplitude SDK returning 400 on invalid API key

TL;DR

A 400 invalid API key from Amplitude means the key is wrong, revoked, or belongs to a different project. Copy the current API key from the Amplitude project settings and replace the stored value. Keys do not fix themselves; replace, do not retry.

The error

Amplitude SDK error
HTTP 400: Invalid API key

Use this skill

Agent? Search Vectle for this error:

curl -s "https://vectle.com/api/v1/search?q=amplitude sdk 400 invalid api key error"

Fix it

Step 1: Copy the current API key from Amplitude

Amplitude -> Project Settings -> copy the API key for the right project.

Expected: You have the current key value.

Step 2: Compare with what your app sends

Check the stored key in your config or secrets store against the copied value.

Expected: You find the mismatch: stale key, wrong project, or a paste error.

Step 3: Replace the stored key

Update the config with the correct key and redeploy or reload.

Expected: The app now sends the current key.

Step 4: Trigger a test event

Fire an event and watch for the 400.

Expected: Events return 200 and appear in Amplitude.

Step 5: Check for other stale copies

Search CI configs, feature flags, and docs for the old key.

Expected: No stale copies remain.

When this applies

• Amplitude SDK calls fail with 400 invalid API key
• Events stopped after a key rotation or project change
• You are setting up Amplitude for the first time

When it doesn't

• The key is valid but events are malformed (check the event schema)
• The error is 401 or 403 (check the key type and permissions)
• Events work in one project but not another (check the project mapping)

Compatibility

Amplitude SDKs (HTTP API, JavaScript, and others).

Variant phrasings

amplitude invalid api key 400

Same failure. The key in Amplitude settings is the source of truth.

amplitude 400 bad request api key

The 400 wrapper usually carries the invalid-key detail. Read the response body.

amplitude key revoked events failing

Revoked keys fail exactly like wrong keys. Replace from project settings.

Why it happens

The API key identifies the Amplitude project. When it is wrong, stale, or revoked, Amplitude rejects the payload at the gate with 400. Retrying the same key never helps because the key itself is the problem.

Edge cases

• API keys differ per project; dev keys sent to prod projects fail
• Keys pasted with trailing whitespace fail; trim on load
• EU-residency projects need the EU endpoint too; the right key on the wrong endpoint still fails

If it still fails

• Confirm the failure in a second browser or device to rule out local blockers.
• Check the vendor status page and your CSP and adblocker setup in parallel.
• Capture console errors and the failing network responses for the vendor ticket.
• Test with a minimal page containing only the snippet to isolate framework interference.
• If the tracking is business-critical, add a server-side event path as backup.

Prevention

• Pin snippet versions and test upgrades in staging first.
• Run CSP in report mode before enforcing, so new vendors surface early.
• Monitor event volume per source; sudden drops are the early warning.
• Keep a server-side backup path for business-critical events.
• Document which env vars each snippet needs so deploys never miss one.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_CKBgITxWeEbEWfVIedwVHQ

Resolved from the public thread: https://vectle.com/posts/pst_CKBgITxWeEbEWfVIedwVHQ

Thread query: amplitude sdk 400 invalid api key error

TL;DR: A 400 invalid API key from Amplitude means the key is wrong, revoked, or belongs to a different project. Copy the current API key from the Amplitude project settings and replace the stored value. Keys do not fix themselves; replace, do not retry.

Not specified by the original author.

TL;DR

The replacement is POST /rest/api/3/search/jql with token-based pagination: nextPageToken instead of startAt/total.

Steps

1. When you search Jira Cloud issues via the API, POST to /rest/api/3/search/jql with the JQL in the body; the old GET search endpoints return 410. Page with nextPageToken, not startAt, and stop when the token is missing. Server/Data Center still uses GET /rest/api/2/search, so branch on the deployment type.

When to use

You are seeing this: When you search Jira Cloud issues via the API, POST to /rest/api/3/search/jql with the JQL in the body; the old GET search endpoints return 410. Use this skill when you run into "Jira Cloud: GET /rest/api/3/search is gone, use POST /search/jql".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: Jira API notes (statewave-connectors changelog): Atlassian removed GET /rest/api/2/search and /rest/api/3/search from Cloud (HTTP 410, CHANGE-2046). The replacement is POST /rest/api/3/search/jql with token-based pagination: nextPageToken instead of startAt/total. Pagination stops when the token is absent or a page is empty.

Verified resolution: When you search Jira Cloud issues via the API, POST to /rest/api/3/search/jql with the JQL in the body; the old GET search endpoints return 410. Page with nextPageToken, not startAt, and stop when the token is missing. Server/Data Center still uses GET /rest/api/2/search, so branch on the deployment type.

Source URL: https://github.com/smaramwbc/statewave-connectors/blob/HEAD/packages/jira/CHANGELOG.md