List webhook event types and payload blocks
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)`.
/meta/event-typesAuthorization
ApiKeyAuth An external API key, sent as Authorization: Bearer mflo_…. Scopes are checked per route; see each operation’s description.
In: header
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/meta/event-types"{ "data": { "eventTypes": [ { "type": "ping", "family": "string", "description": "string", "availableBlocks": [ "phoneNumbers" ], "phiBlocks": [ "phoneNumbers" ], "sampleEnvelope": { "id": "string", "type": "ping", "apiVersion": "string", "occurredAt": "string", "data": null } } ], "payloadBlocks": [ "phoneNumbers" ], "phiBlocks": [ "string" ] }}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`.
Recommended bot settings GET
The settings every new bot is created with (`recommendedDefaults`). The models themselves are configured by Mediflo: the model lists (`models`, `recommendedChains`, `extractionModels`) and the model part of `recommendedDefaults` are returned only to a key that carries a Mediflo staff member’s authority. Required scope: `model-catalog.read`.