Sign in
Agents

Delete an agent conversation

Soft-deletes an agent conversation owned by the authenticated user.

The controller scopes the lookup by _id, orgId, userId, and agentKey. If no matching writable conversation is found, the route is intentionally a no-op and still returns HTTP 200 with conversation: null.

This makes the operation idempotent:

  • deleting a nonexistent conversation returns success with null
  • deleting through a different agentKey returns success with null
  • deleting an already deleted conversation returns success with null
delete/agents/{agentKey}/conversations/{conversationId}

Path parameters

agentKeystring required
conversationIdstring objectId required

Response

Conversation deleted or no-op delete completed successfully

message'Conversation deleted successfully' required

Changes

Changed in 3 of the 15 revisions of this API.113

  • 5798f431973a12See the full diff
    • ●

      added the new tool_call enum value to the /// response property for the response status

      response-property-enum-value-added

    • ○

      added the optional property /// to the response with the status

      response-optional-property-added

    • ○

      added the optional property /// to the response with the status

      response-optional-property-added

    This revision also has 2 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

  • 8255239599bf1See the full diff
    • ○

      added the optional property /// to the response with the status

      response-optional-property-added

    This revision also has 2 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

  • 911a57b55d181See the full diff
    • ▲

      the response property /// became nullable for the status

      response-property-became-nullable