PUThttps://core-api.heysadie.ai/assistants/{id}/tools/{toolId}/steps/{stepId}/override

Set step instruction override

Override a single step in a tool's instruction flow **for a specific assistant**. This allows you to customize how a shared tool behaves for one assistant, without modifying the tool itself (which would affect all other assistants using it). ### How it works Each step in a tool's `instruction.steps` array can have a `step_id` field — a stable, internal identifier that never appears in the prompt. You use that `step_id` to target which step to override. ### What you can override per step | Field | Type | Description | |-------|------|-------------| | `action` | string | Replace the step's action text | | `additional_rules` | string[] | Replace the step's additional rules | | `wait_for_response` | boolean | Change whether the assistant waits for a caller response | Only include the fields you want to change. Omitted fields keep the tool's default value. ### Removing a step entirely To remove a step from this assistant's flow (so it is skipped entirely), send: ```json { "_remove": true } ``` ### Requirements - The **assistant** must belong to your tenant. - The **tool** must belong to your tenant (or be a global tool). - The **tool must be linked** to the assistant. - The **step_id** must exist in the tool's `instruction.steps` array. ### Example If the tool has a step with `"step_id": "collect_email"`, you can override it for one assistant: ``` PUT /assistants/{id}/tools/{toolId}/steps/collect_email/override { "action": "Just confirm the email already on file.", "additional_rules": ["Skip if email is already confirmed."] } ``` Other assistants using the same tool will still see the original step.

curl -X PUT "https://core-api.heysadie.ai/assistants/ASSISTANT_ID/tools/TOOL_ID/steps/STEP_ID/override" \
  -H "Authorization: ApiKey YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "action": "string",
    "additional_rules": [
      "string"
    ],
    "wait_for_response": true
  }'