Delete an AI project

DELETE 
/ai/projects/:project_id

Starts deleting an AI project in the background. You must be an owner of the project. The project status is set to deleting and the work is queued. A 200 means deletion was accepted, not that it has finished — poll GET /ai/projects/{project_id} until it returns 404. If background deletion fails, status becomes delete-failed and Message holds the error. The original call still returned 200. Deletion removes the project's data, chats, comments, avatar, guard-rail link, and access entries. Notes are detached from the project but not deleted. Linked knowledge bases and agents are unlinked, not deleted. Calling this again after the project is gone returns 400.

Request

Responses

200

Deletion was accepted and is running in the background. The project is not gone yet; ProjectStatus is deleting.

Response Headers

Access-Control-Allow-Origin
Access-Control-Allow-Methods
Access-Control-Allow-Headers
Strict-Transport-Security

400

The request was invalid, you do not have permission, or deletion could not be started. The body is {"Message": " - "}. Common cases include a missing role_id (AUTH-1001), missing ai.fullaccess permission (AUTH-1030), not being an owner (AUTH-1012), a project that does not exist (IPV-1002, returned as 400 rather than 404), or the background job failing to start (AI-1002; status is delete-failed and you can retry). Permission and not-found cases return 400, not 403 or 404.

Response Headers

Access-Control-Allow-Origin
Access-Control-Allow-Methods
Access-Control-Allow-Headers
Strict-Transport-Security

500

An unexpected server error. The body is typically {"Message": "GE-1008 - Could not complete the request. Please try again."}.

Response Headers

Access-Control-Allow-Origin
Access-Control-Allow-Methods
Access-Control-Allow-Headers
Strict-Transport-Security