Skip to content
Project management & work tracking

developer.atlassian.com

Jira sandbox and mock API

Jira Cloud platform REST API documentation Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
600
Collections
-
Event types
-
Start this simulation Vendor documentation
example request
curl https://your-jira.slurry.io/rest/api/3/announcementBanner \
  -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 600.

  • GET/rest/api/3/announcementBanner
  • PUT/rest/api/3/announcementBanner
  • POST/rest/api/3/app/field/context/configuration/list
  • POST/rest/api/3/app/field/value
  • GET/rest/api/3/app/field/{fieldIdOrKey}/context/configuration
  • PUT/rest/api/3/app/field/{fieldIdOrKey}/context/configuration
  • PUT/rest/api/3/app/field/{fieldIdOrKey}/value
  • GET/rest/api/3/application-properties
  • GET/rest/api/3/application-properties/advanced-settings
  • PUT/rest/api/3/application-properties/{id}
  • GET/rest/api/3/applicationrole
  • GET/rest/api/3/applicationrole/{key}