Jira Teams (via Apideck Proxy)

Access Jira Teams through Apideck's Proxy API with managed Vault auth. Apideck stores credentials, refreshes tokens, and forwards your HTTP calls to Jira Teams's native API — you keep using Jira Teams'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 Teams to a unified-API resource model — your code talks Jira Teams'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-teams
• Mode: Proxy-only (no unified API resources)
• Auth type: basic
• Status: beta
• Apideck setup guide: Connection guide
• Gotchas: page
• Homepage: https://www.atlassian.com

When to use this skill

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