Jira Data Center (via Apideck Proxy)

Access Jira Data Center through Apideck's Proxy API with managed Vault auth. Apideck stores credentials, refreshes tokens, and forwards your HTTP calls to Jira Data Center's native API — you keep using Jira Data Center's own request and response shapes, while Apideck eliminates per-tenant credential plumbing and gives you a single auth integration shared across every Apideck connector.

Auth-only / proxy-only connector. Apideck does not map Jira Data Center to a unified-API resource model — your code talks Jira Data Center's own API directly through the Proxy. You still get Vault credential storage, token refresh, retries, and a consistent request envelope.

Quick facts

• Apideck serviceId: jira-data-center
• Mode: Proxy-only (no unified API resources)
• Auth type: apiKey
• Status: live
• Gotchas: page
• Jira Data Center docs: https://developer.atlassian.com/server/jira/platform/rest/
• Homepage: https://www.atlassian.com/enterprise/data-center/jira

When to use this skill

Activate this skill when the user wants to call Jira Data Center via Apideck — for example, "call the Jira Data Center API" or "fetch data from Jira Data Center". This skill teaches the agent: