How do I mock the Jira Cloud REST API locally?

Install stunt, add a one-service block to stunt.yaml (adapter: embedded:jira-style), and run stunt up. You get a local, stateful stand-in for Jira Cloud REST API 3 — 32 routes over rest — with no remote account, no network, and no bills.

Is the Jira Cloud REST API mock data synthetic?

Yes — entirely. The adapter returns generated data only; stunt's adapter lint rejects real-looking secrets and PII at build time. It simulates the shape and behavior of Jira Cloud REST API (routes, status codes, pagination, webhooks), never real records.

← all adapters

jira-style

simulates Jira Cloud REST API 3

restadapter v0.1.032 routes

verification

SDKverified with jira-js 6.1.0 (floor)· surface 32 · not implemented 5 · differs 6

use it

# add to stunt.yaml
services:
  jira:
    adapter: embedded:jira-style

# then
$ stunt up

The embedded: source extracts this adapter from the binary — no git clone, fully offline.

how to mock the Jira Cloud REST API locally

Install stunt, paste the service block above into stunt.yaml, run stunt up — then point your client at localhost instead of Jira Cloud REST API. It works offline, keeps state across requests and restarts, and every response is synthetic: the route shapes, status codes, pagination, and webhook delivery follow the real Jira Cloud REST API 3 surface — the data is fake, the behavior is real.

backing stores

issuesprojectscommentstransitions

api surface (32)

generated from the adapter manifest — exactly what boots, nothing more · covers 3% of the real API's 634 routes (derived from sdk jira-js @ 6.1.0 (floor))

32 routes

GET/rest/api/3/myself

GET/rest/api/3/serverInfo

GET/rest/api/3/project

GET/rest/api/3/project/search

GET/rest/api/3/project/{key}

POST/rest/api/3/search/jql

GET/rest/api/3/search

POST/rest/api/3/issue

GET/rest/api/3/issue/{key}

PUT/rest/api/3/issue/{key}

DELETE/rest/api/3/issue/{key}

GET/rest/api/3/issue/{key}/transitions

POST/rest/api/3/issue/{key}/transitions

POST/rest/api/2/issue

GET/rest/api/2/issue/{key}

PUT/rest/api/2/issue/{key}

DELETE/rest/api/2/issue/{key}

GET/rest/api/2/issue/{key}/transitions

POST/rest/api/2/issue/{key}/transitions

GET/rest/api/2/issue/{key}/comment

GET/rest/api/2/issue/{key}/comment/{id}

POST/rest/api/2/issue/{key}/comment

PUT/rest/api/2/issue/{key}/comment/{id}

DELETE/rest/api/2/issue/{key}/comment/{id}

GET/rest/api/3/issue/{key}/comment

GET/rest/api/3/issue/{key}/comment/{id}

POST/rest/api/3/issue/{key}/comment

PUT/rest/api/3/issue/{key}/comment/{id}

DELETE/rest/api/3/issue/{key}/comment/{id}

POST/rest/api/3/webhook

GET/rest/api/3/webhook

DELETE/rest/api/3/webhook

SDK-verified behaviors (7)

✓myself + project resolve
✓create assigns a TEST-n key
✓get round-trips; edit persists
✓JQL search finds it
✓add comment + list
✓transition moves the status
✓delete removes it

Not implemented (5)

No attachments, worklogs, watchers, or issue link endpoints
No project create/update, versions, or components endpoints
No agile boards, sprints, or backlog endpoints
No users search, avatars, or notification endpoints
No workflow or field configuration management endpoints

Differs from the real API (6)

Comment bodies are plain strings, not Atlassian Document Format objects
Enhanced-search nextPageToken is a plain decimal offset, not an opaque token
JQL subset: parenthesised grouping unsupported; unknown fields 400
JQL dates compare as ISO-8601 strings, not parsed datetimes
Single fixed simplified workflow for all projects; real workflows are configurable
GET /rest/api/3/webhook (list registrations) marked simulator-only

full scorecard →

want more of the Jira Cloud REST API surface? adapters are YAML + Starlark — the authoring guide covers adding routes, fixtures, and state machines. Open an issue for anything big first, or just file a PR — merged routes ship in the next release.