Mediflo
REST APISupport tickets

Get a support ticket

Required scope: `tickets.read`.

GET/tickets/{ticketId}

Authorization

ApiKeyAuth
AuthorizationBearer <token>

An external API key, sent as Authorization: Bearer mflo_…. Scopes are checked per route; see each operation’s description.

In: header

Path Parameters

ticketId*string
Formatuuid

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

curl -X GET "https://example.com/tickets/497f6eca-6276-4993-bfeb-53cbbbba6f08"
{  "data": {    "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",    "title": "string",    "description": "string",    "status": "OPEN",    "priority": "LOW",    "category": "BUG",    "awaitingResponse": "REPORTER",    "reportedByUserId": "dd32a358-6c1f-42bb-a796-4d4e1e45691d",    "reportedVia": "string",    "contextUrl": "string",    "linkedSessions": [      {        "resourceType": "BOT_SESSION",        "resourceId": "string",        "note": "string"      }    ],    "createdAt": "2019-08-24T14:15:22Z",    "updatedAt": "2019-08-24T14:15:22Z",    "resolvedAt": "2019-08-24T14:15:22Z"  }}

Hold a slot for a few minutes POST

A hold belongs to the REQUEST that created it, and only the same owner can book it or release it. Send `X-Mediflo-Scheduling-Session` and repeat the SAME value on the POST /scheduling/appointments that consumes this hold and on DELETE /scheduling/holds/{holdId} — without the header each request is its own owner, so the hold you just created can neither be booked nor released and simply expires. Required scope: `scheduling.book`.

List support tickets GET

Required scope: `tickets.read`.