jira-service-desk
Installation
SKILL.md
Jira Service Desk (via Apideck Proxy)
Access Jira Service Desk through Apideck's Proxy API with managed Vault auth. Apideck stores credentials, refreshes tokens, and forwards your HTTP calls to Jira Service Desk's native API — you keep using Jira Service Desk'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 Service Desk to a unified-API resource model — your code talks Jira Service Desk'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-service-desk - Mode: Proxy-only (no unified API resources)
- Auth type: oauth2
- Status: beta
- Apideck setup guide: OAuth credentials
- Gotchas: page
- Jira Service Desk docs: https://developer.atlassian.com/cloud/jira/service-desk/rest/intro/
- Homepage: https://www.atlassian.com/software/jira/service-management