Jira Service Management
Atlassian's service desk: requests, customers, queues and SLAs
- Connects by
- Signing in with Atlassian
- Category
- Support
- Part of
- Atlassian
- Tools
- 74
| Service | Key | Base URL |
|---|---|---|
| Jira Service Management | jira-service-management | https://api.atlassian.com/ex/jira/{cloud_id}/rest/servicedeskapi |
Connecting
Your client presses Connect on their link and approves on Atlassian's own screen. Operate As never sees their password.
curl https://api.operate.as/v1/me/clients \ -H "Authorization: Bearer $OPERATE_AS_API_KEY"[ { "id": "6f1c2a7e-...", "name": "Miller Dental", "services": [ "jira-service-management" ] }]Permissions
| What the client reads | Permission it asks for |
|---|---|
| See your service desks and requests | read:servicedesk-request |
| Create and comment on requests | write:servicedesk-request |
| Add and manage your service desk customers | manage:servicedesk-customer |
Tools
Install Jira Service Management's typed package for your language:
pip install operate-as-jira-service-managementjira-service-management.add_customerscurl -X POST https://api.operate.as/v1/actions/jira-service-management.add_customers \ -H "Authorization: Bearer $OPERATE_AS_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "clientId": "6f1c2a7e-...", "input": { "service_desk_id": "<service_desk_id>" } }'Shows the required inputs. Every input, with its JSON Schema: GET /v1/actions/jira-service-management.add_customers
{ "status": 200, "data": { "…": "the service's own response" }, "encoding": "json"}Pass-through
Paths continue from https://api.atlassian.com/ex/jira/{cloud_id}/rest/servicedeskapi, with the parts in braces filled in from your client's account. Your Operate As key goes in Authorization; the client's access is added for you.
See Pass-through requests for the full request and response format.
curl "https://api.operate.as/v1/clients/6f1c2a7e-.../jira-service-management/..." \ -H "Authorization: Bearer $OPERATE_AS_API_KEY"{ "status": 200, "data": { "…": "the service's own response" }, "encoding": "json"}When access ends
Operate As renews the sign-in before it runs out and checks it daily. If Atlassian refuses to renew it, the service shows Expired, you're alerted, and your client reconnects from the same link.
See Keeping access alive and Removing access.
HTTP/1.1 409 ConflictContent-Type: application/json{ "detail": "Miller Dental's Atlassian access ended. Send them their link to reconnect."}{ "id": "evt_3f9a1c…", "type": "connection.expired", "createdAt": "2026-10-16T08:00:00+00:00", "data": { "clientId": "6f1c2a7e-...", "clientName": "Miller Dental", "provider": "atlassian", "services": [ "jira-service-management" ], "reconnectUrl": "https://…" }}