Skip to main content
DELETE
Delete Disposition
Dispositions are enabled per organization. If your organization does not have them, every route under /dispositions returns 404.

Overview

Retires a disposition. It is disabled and marked deleted, so it stops running on new calls and no longer appears in List Dispositions. Results already recorded on past calls are left alone. The call is idempotent: deleting a disposition that is already deleted succeeds and returns the same body, so a retry after a dropped connection is safe. Requires an admin, owner, operator, or prompter role.

Headers

string
required
Your API key for authentication.

Path Parameters

string
required
The agent’s unique identifier. Must be a UUID.
string
required
The disposition’s unique identifier. Must be a UUID, and must belong to this agent. Returns 404 NOT_FOUND otherwise.

Response

string
The disposition that was deleted. Matches {disposition_id}.
null | array
null on success, or a list of error objects if the request failed. Returns 409 CONFLICT when the disposition changed while the delete was in flight; read it again and retry.

Docs for agents: llms.txt