Mediflo
REST APIProcedures

Reorder a bot’s procedures

Pass EVERY non-deleted procedure id exactly once. A partial list is refused rather than merged: position also drives the node ids of the compiled call flow, so a duplicate position is a compile-level ambiguity. Order does not decide which free-form procedure the model reaches for — the trigger does. Required scope: `bots.write`.

POST/bots/{botId}/procedures/reorder

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

botId*string
Formatuuid

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

application/json

application/json

curl -X POST "https://example.com/bots/497f6eca-6276-4993-bfeb-53cbbbba6f08/procedures/reorder" \  -H "Content-Type: application/json" \  -d '{    "procedureIds": [      "2553a8c1-eab0-4f76-873c-4e97329ef9b7"    ]  }'
{  "data": [    {      "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",      "botId": "58ed41f0-04bf-402f-9853-7143ef7dd5ce",      "name": "string",      "type": "FREE_FORM",      "trigger": "string",      "content": null,      "position": 0,      "enabled": true,      "createdAt": "2019-08-24T14:15:22Z",      "updatedAt": "2019-08-24T14:15:22Z"    }  ],  "pagination": {    "page": 0,    "limit": 0,    "total": 0,    "totalPages": 0  }}

Edit a procedure PATCH

Only the fields you send are touched, but the WHOLE procedure is re-validated, so a rename cannot leave a body that breaks its tier’s rules. `type` cannot be changed — the content shape depends on it; delete and re-create instead. `enabled: false` is the one change that takes effect WITHOUT a publish: it is checked live at dispatch, even against an already-published snapshot. Required scope: `bots.write`.

Create a procedure POST

FREE_FORM REQUIRES a `trigger`; DETERMINISTIC must have none (the model can never choose to run one). Procedures are part of the configuration snapshot: this reaches no call until POST /bots/{botId}/config/publish. To make a deterministic procedure the call flow, set `entryProcedureId` via PATCH /bots/{botId}/config afterwards. Required scope: `bots.write`.