Skip to content
Helpdesk & ticketing

dac-static.atlassian.com

Jira Service Management sandbox and mock API

Public REST API for Jira Service Management Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
75
Collections
-
Event types
-
Start this simulation Vendor documentation
example request
curl https://your-jira-service-management.slurry.io/rest/servicedeskapi/assets/workspace \
  -H "Authorization: Bearer slurry_sim_..."

Your simulation gets its own hostname, key and IP allow-list. Built from API version 1001.0.0-SNAPSHOT-44cdd07c042959317ed5591bf79dbcd9369f3610.

What gets simulated

Collections, relationships and state machines are worked out from the spec when you start the simulation.

  • State. Creates, updates and deletes persist and show up in later reads.
  • Behaviour. Records move through their states on a schedule you control, and you can fast-forward up to 30 days.
  • Webhooks. Every change emits a signed, retried event.
  • Failure. Per-endpoint errors, latency and chaos rules, on demand.

Operations

First 12 of 75.

  • GET/rest/servicedeskapi/assets/workspace
  • POST/rest/servicedeskapi/customer
  • POST/rest/servicedeskapi/customer/skip-permission-check
  • PUT/rest/servicedeskapi/customer/user/{accountId}/revoke-portal-only-access
  • GET/rest/servicedeskapi/info
  • GET/rest/servicedeskapi/insight/workspace
  • GET/rest/servicedeskapi/knowledgebase/article
  • GET/rest/servicedeskapi/knowledgebase/article/view/{pageId}
  • GET/rest/servicedeskapi/organization
  • POST/rest/servicedeskapi/organization
  • GET/rest/servicedeskapi/organization/{organizationId}
  • DELETE/rest/servicedeskapi/organization/{organizationId}