API template library

Simulate the Jira Cloud platform API

A WireMock simulation of Atlassian's REST API — covering issues, comments and worklogs, projects, workflows and schemes, custom fields, users and groups, filters, dashboards, and webhooks.

Vendor
Atlassian
Functionality
Issues, projects, workflows, custom fields
Endpoints
630
Stubs
769
Protocol
REST
Validation
AI-validated Before publication, an AI agent exercised these endpoints against the real Atlassian API through WireMock's recording proxy, and the recorded traffic was used to verify each stub's request and response shapes.

Live sandbox · no signup, no API key

Jira Cloud Platform

A running WireMock Cloud instance of this template, callable right now from a terminal, a script, or an AI agent.

Base URL
https://d75w0w.wiremockapi.cloud

GET Get advanced settings [getAdvancedSettings]

curl -s -X GET 'https://d75w0w.wiremockapi.cloud/rest/api/3/application-properties/advanced-settings'

PUT Update fields associated with field schemes [updateFieldsAssociatedWithSchemes]

curl -s -X PUT 'https://d75w0w.wiremockapi.cloud/rest/api/3/config/fieldschemes/fields' \
  -H 'Content-Type: application/json' \
  -d '{}'

DELETE Remove fields associated with field schemes [removeFieldsAssociatedWithSchemes]

curl -s -X DELETE 'https://d75w0w.wiremockapi.cloud/rest/api/3/config/fieldschemes/fields'
Method Path Summary
POST /rest/api/3/agents/bulk/invoke/batch Bulk start agent sessions (batch)
POST /rest/api/3/agents/bulk/invoke/uniform Bulk start agent sessions (uniform)
GET /rest/api/3/announcementBanner Get announcement banner configuration
PUT /rest/api/3/announcementBanner Update announcement banner configuration
GET /rest/api/3/app/field/{fieldIdOrKey}/context/configuration Get custom field configurations
PUT /rest/api/3/app/field/{fieldIdOrKey}/context/configuration Update custom field configurations
PUT /rest/api/3/app/field/{fieldIdOrKey}/value Update custom field value
POST /rest/api/3/app/field/context/configuration/list Bulk get custom field configurations
POST /rest/api/3/app/field/value Update custom fields
GET /rest/api/3/application-properties Get application property
PUT /rest/api/3/application-properties/{id} Set application property
GET /rest/api/3/application-properties/advanced-settings Get advanced settings
GET /rest/api/3/applicationrole Get all application roles
GET /rest/api/3/applicationrole/{key} Get application role
DELETE /rest/api/3/attachment/{id} Delete attachment
GET /rest/api/3/attachment/{id} Get attachment metadata
GET /rest/api/3/attachment/{id}/expand/human Get all metadata for an expanded attachment
GET /rest/api/3/attachment/{id}/expand/raw Get contents metadata for an expanded attachment
GET /rest/api/3/attachment/content/{id} Get attachment content
GET /rest/api/3/attachment/meta Get Jira attachment settings
GET /rest/api/3/attachment/thumbnail/{id} Get attachment thumbnail
GET /rest/api/3/auditing/record Get audit records
GET /rest/api/3/avatar/{type}/system Get system avatars by type
POST /rest/api/3/bulk/issues/delete Bulk delete issues
GET /rest/api/3/bulk/issues/fields Get bulk editable fields
POST /rest/api/3/bulk/issues/fields Bulk edit issues
POST /rest/api/3/bulk/issues/move Bulk move issues
GET /rest/api/3/bulk/issues/transition Get available transitions
POST /rest/api/3/bulk/issues/transition Bulk transition issue statuses
POST /rest/api/3/bulk/issues/unwatch Bulk unwatch issues
POST /rest/api/3/bulk/issues/watch Bulk watch issues
GET /rest/api/3/bulk/queue/{taskId} Get bulk issue operation progress
POST /rest/api/3/changelog/bulkfetch Bulk fetch changelogs
GET /rest/api/3/classification-levels Get all classification levels
GET /rest/api/3/comment/{commentId}/properties Get comment property keys
DELETE /rest/api/3/comment/{commentId}/properties/{propertyKey} Delete comment property
GET /rest/api/3/comment/{commentId}/properties/{propertyKey} Get comment property
PUT /rest/api/3/comment/{commentId}/properties/{propertyKey} Set comment property
POST /rest/api/3/comment/list Get comments by IDs
GET /rest/api/3/component Find components for projects
POST /rest/api/3/component Create component
DELETE /rest/api/3/component/{id} Delete component
GET /rest/api/3/component/{id} Get component
PUT /rest/api/3/component/{id} Update component
GET /rest/api/3/component/{id}/relatedIssueCounts Get component issues count
GET /rest/api/3/config/fieldschemes Get field schemes
POST /rest/api/3/config/fieldschemes Create field scheme
DELETE /rest/api/3/config/fieldschemes/{id} Delete a field scheme
GET /rest/api/3/config/fieldschemes/{id} Get field scheme
PUT /rest/api/3/config/fieldschemes/{id} Update field scheme
POST /rest/api/3/config/fieldschemes/{id}/clone Clone field scheme
GET /rest/api/3/config/fieldschemes/{id}/fields Search field scheme fields
GET /rest/api/3/config/fieldschemes/{id}/fields/{fieldId}/parameters Get field parameters
GET /rest/api/3/config/fieldschemes/{id}/projects Search field scheme projects
DELETE /rest/api/3/config/fieldschemes/fields Remove fields associated with field schemes
PUT /rest/api/3/config/fieldschemes/fields Update fields associated with field schemes
DELETE /rest/api/3/config/fieldschemes/fields/parameters Remove field parameters
PUT /rest/api/3/config/fieldschemes/fields/parameters Update field parameters
GET /rest/api/3/config/fieldschemes/projects Get projects with field schemes
PUT /rest/api/3/config/fieldschemes/projects Associate projects to field schemes

+570 more endpoints in the full spec.

Unauthenticated WireMock Cloud demo sandbox for Atlassian — not an official Atlassian sandbox, and it returns simulated example data only.

What's inside the Jira Cloud template

The template mirrors version 3 of the Jira Cloud platform REST API, the surface Atlassian documents under /rest/api/3. Creating an issue answers 201 with a numeric id, a key built from the project key you sent (EX in, EX-024 out) and a self link; fetching that id returns the full issue document with your summary, labels and Atlassian Document Format description stored, and status set to To Do. Integrations that parse fields.status, fields.labels and ADF bodies from real Jira read these responses unchanged.

  • Issues — create, edit, transition, link, watch, vote and bulk-fetch, with attachments and issue links reflected on the issue itself
  • Comments, worklogs and properties — threaded comments in ADF, time tracking entries, and entity properties on issues, projects, users and dashboard items
  • Projects and their parts — components, versions, roles, categories and project-level settings
  • Workflows and schemes — statuses, screens, workflow schemes with draft publishing, and permission, notification and security schemes
  • Custom fields — field contexts, options, default values and the trash, including app-provided fields
  • Users, groups, filters and dashboards — group membership kept consistent from both sides, saved JQL filters, dashboards and webhooks

Jira Cloud platform mock API FAQ

No. The sandbox doesn't authenticate requests, so neither basic auth nor an OAuth bearer token is checked. Keep real Atlassian tokens out of it all the same: it's a public endpoint shared by everyone who visits this page.

The template stores issues under their numeric id. The create response carries both the id and the key, so address follow-up calls (get, edit, comment, transition) with the id. Comments posted that way read back from the issue's comment list straight away.

No. The sandbox keeps one shared state store, so an issue, project or group you create is visible to the next caller, and nothing resets on a schedule. Create the template in WireMock Cloud for a private store with a "Reset state" button between test runs.

Read-only endpoints with nothing to derive from state, such as server info, licence details, JQL tooling and audit records, answer the examples from Atlassian's spec, placeholder strings included. If a test depends on a specific search result or audit entry, stub that response in your own copy.

Vendor names identify APIs represented by WireMock template sources. This page does not imply vendor endorsement, certification, partnership, or official integration status.