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
ServiceKey
Jira Service Managementjira-service-management

Connecting

Your client presses Connect on their link and approves on Atlassian's own screen. Operate As never sees their password.

Check they're connected
curl https://api.operate.as/v1/me/clients \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"
Response
[  {    "id": "6f1c2a7e-...",    "name": "Miller Dental",    "services": [      "jira-service-management"    ]  }]

Permissions

What the client readsPermission it asks for
See your service desks and requestsread:servicedesk-request
Create and comment on requestswrite:servicedesk-request
Add and manage your service desk customersmanage:servicedesk-customer

Tools

Install Jira Service Management's typed package for your language:

pip install operate-as-jira-service-management
Run jira-service-management.add_customers
curl -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

Response
{  "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.

Call any endpoint
curl "https://api.operate.as/v1/clients/6f1c2a7e-.../jira-service-management/..." \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"
Response
{  "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.

Calls answer
HTTP/1.1 409 ConflictContent-Type: application/json{  "detail": "Miller Dental's Atlassian access ended. Send them their link to reconnect."}
Your webhook receives
{  "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://…"  }}