Skip to main content
DELETE
/
api
/
v1
/
assistant-graphs
/
{graph_id}
curl -X DELETE https://api.burki.dev/api/v1/assistant-graphs/1 \
  -H "Authorization: Bearer YOUR_API_KEY"
{
  "success": true,
  "message": "Assistant graph 'Customer Service Router' deleted successfully"
}
Permanently delete an assistant graph along with all its nodes, edges, and conversation session data. This action cannot be undone.

Path Parameters

graph_id
integer
required
The unique identifier of the graph to delete.

Response

success
boolean
Whether the deletion was successful.
message
string
Confirmation message with the deleted graph name.
curl -X DELETE https://api.burki.dev/api/v1/assistant-graphs/1 \
  -H "Authorization: Bearer YOUR_API_KEY"
{
  "success": true,
  "message": "Assistant graph 'Customer Service Router' deleted successfully"
}

Error Responses

Status CodeDescription
401Unauthorized - Invalid or missing API key
404Graph not found in your organization
500Server error deleting the graph

Side Effects

When you delete a graph:
The following data is permanently deleted:
  • All nodes in the graph
  • All edges in the graph
  • All conversation session records
  • All intent detection logs for those sessions
The following data is NOT deleted:
  • The underlying assistants (they remain available for other graphs or direct use)
  • Phone numbers (they are unassigned from the graph but not deleted)
  • Call records (they remain for billing and analytics purposes)

Best Practices

1

Check Active Calls

Before deleting a graph, ensure there are no active calls using it. Deleting a graph during active calls may cause unexpected behavior.
2

Unassign Phone Numbers First

Consider explicitly unassigning phone numbers before deletion to ensure they’re properly reconfigured.
3

Export Data If Needed

If you need conversation session data for analytics, export it before deletion using the sessions endpoint.
4

Consider Deactivation

If you may need the graph later, consider setting is_active: false instead of deleting.