Attach more bot sessions to a ticket
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`.
/tickets/{ticketId}/sessionsAuthorization
ApiKeyAuth An external API key, sent as Authorization: Bearer mflo_…. Scopes are checked per route; see each operation’s description.
In: header
Path Parameters
uuidRequest 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/497f6eca-6276-4993-bfeb-53cbbbba6f08/sessions" \ -H "Content-Type: application/json" \ -d '{ "botSessionIds": [ "6bb3380b-3bc4-451c-8434-88210aaae620" ] }'{ "data": { "ticketId": "e3e3e8ea-b02a-4536-85a2-a9c90f4ee74f", "linkedSessions": [ { "resourceType": "BOT_SESSION", "resourceId": "string", "note": "string" } ] }}List support tickets GET
Required scope: `tickets.read`.
File a support ticket with Mediflo POST
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`.