get
https://example.com
POST /v2/cases/actions/create-ticket — Create a ticket-style case (no order)
Recent Requests
Log in to see full request history
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Loading…
Creates a general support case not tied to an order. This is not a simple alias for POST /v2/cases — it runs a different validation path: the request type must have at least one JSM field synced (422 if not), and field values are supplied differently (see below).
Request body
| Field | Type | Required | Description |
|---|---|---|---|
requestTypeId | string | Yes | JSM request type ID — the externalCaseTypeIdentifier from GET /v2/jira-apis/request-types |
fields | object | No | Map of externalSystemIdentifier → value |
requestFieldValues | object | No | Additional field values, merged with fields |
Unlike POST /v2/cases, there is no orderId and no order/patient variable resolution — only the field values you provide (or the request type's defaults) are sent to Jira.
Response 201
201Same response shape as POST /v2/cases ({ success, missingRequiredFields, data }) — see that page for field details.
Errors
| Status | Code | Description |
|---|---|---|
| 422 | INVALID_FIELD | requestTypeId missing, or the request type has no synced JSM fields (sync it first via POST /v2/cases/sync-case-type) |
| 404 | — | Request type not found |
Required role
affiliate_super_admin, affiliate_admin, or affiliate_agent