File a support ticket with Mediflo
Attach the bot sessions that ARE the problem via `botSessionIds` — each id is validated against your tenant, and an unknown one is a 422 naming it. `reportedByUserId` is OPTIONAL: pass it when you know who is reporting (resolve one with `GET /users`) and the ticket is attributed to that person; omit it and the ticket is credited to the person who created the API key, still with `reportedVia: "external_api"`. Only a system key with no human creator files with no reporter. Required scope: `tickets.write`.
/ticketsAuthorization
ApiKeyAuth An external API key, sent as Authorization: Bearer mflo_…. Scopes are checked per route; see each operation’s description.
In: header
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
curl -X POST "https://example.com/tickets" \ -H "Content-Type: application/json" \ -d '{ "title": "string", "description": "string" }'{ "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" }}Attach more bot sessions to a ticket POST
The "it keeps happening" flow. Re-attaching a session already on the ticket is a no-op, not an error, so a retry is safe. Required scope: `tickets.write`.
List webhook event types and payload blocks GET
Any valid API key may read this — it is contract metadata, not tenant data. The event list depends on the features enabled for your organisation: event families of areas it has not enabled (e.g. `case.*`) are left out, so do not cache the response across organisations. `phiBlocks` marks the blocks that carry personal data, including sensitive data. Required scope: `(any valid key)`.