# Jira Service Desk — Issue Tracking API: overview

> Canonical URL: https://developers.apideck.com/apis/issue-tracking/jira-service-desk/overview

IT service desk and customer service software by Jira Service Desk. Powerful ticketing system used by 25,000+ organizations today.
- Status: beta
- Authentication: oauth2

- **environment notes:**   - **environment:** Single environment
  - **description:** Testing and production share the same credential shape, so there is no separate test service. Connect a site you are willing to write to, and keep trial runs away from one people rely on.
- **apideck credentials available:** true
- **account type required:** A Jira Service Management site on Atlassian Cloud.
- **difficulty reason:** Self-Service OAuth App + No Dedicated Sandbox
- **external guides:**   - **source:** Atlassian
  - **title:** Jira Service Management Cloud REST API
  - **url:** https://developer.atlassian.com/cloud/jira/service-desk/rest
  - **title:** Atlassian OAuth 2.0 (3LO) apps
  - **source:** Atlassian
  - **url:** https://developer.atlassian.com/cloud/jira/service-desk/oauth-2-authorization-code-grants-3lo-for-apps/
  - **url:** https://developer.atlassian.com/cloud/jira/platform/rate-limiting/
  - **source:** Atlassian
  - **title:** Jira Cloud rate limiting
- **partnership portal name:** Atlassian developer console
- **sandbox available:** false
- **webhooks:** No webhooks - poll for changes instead.
- **important to know:** Jira Service Desk is an auth-only connector: there are no unified Issue Tracking endpoints. Apideck handles the OAuth connection, and every read and write goes through the Proxy API against Atlassian's own Service Desk API shape.
The hourly request quota belongs to the app, not to each connected site: every site draws from the same pool by default, so later consumers compete with earlier ones.
- **partnership note:** Registering your own OAuth 2.0 app there gives you the client ID and secret.
- **partnership url:** https://developer.atlassian.com/console/myapps/
- **sandbox note:** Test on a free Jira Service Management site (up to three agents).
- **responsibility matrix:**   - **customer:** ✓
  - **area:** Create Atlassian developer account
  - **area:** Register OAuth app, grant Service Desk scopes and set the callback URL
  - **apideck:** Docs provided
  - **customer:** ✓
  - **area:** Add credentials to Apideck
  - **customer:** ✓
  - **area:** Authorise connection (OAuth)
  - **consumer:** ✓
  - **apideck:** Handles OAuth flow
  - **consumer:** ✓ (only when they can reach more than one)
  - **area:** Choose the Atlassian site
  - **apideck:** ✓ Resolves it automatically for a single site
  - **customer:** ✓ Builds the requests
  - **area:** Call Jira Service Desk data via the Proxy API
  - **apideck:** ✓ Routes and authenticates
  - **area:** Monitor connections
  - **customer:** ✓ Via the Apideck Dashboard
  - **apideck:** Logs and alerts
  - **consumer:** ✓ Can revoke at any time
- **authentication note:** Authorization Code flow.
- **beta:** true
- **difficulty:** moderate
- **rate limits:** 65,000 points an hour, enforced since 2 March 2026, plus per-second burst limits. Listing customers on a service desk is capped at 5 requests a second.
- **apideck credentials note:** Apideck's test credentials, for trying the connection; production connections use your own OAuth app.
- **consumer access level:** A Jira user on the site who can authorise the app; the connection then reaches what that user can already see.
- **partnership required:** false

## Supported resources



An omitted operation list does not establish operation support. Verify the selected operation in the coverage matrix.

[API reference](https://developers.apideck.com/apis/issue-tracking/reference.md) · [Coverage matrix](https://developers.apideck.com/apis/issue-tracking/coverage)