Delete AI Content-Safety Category

Endpoint

DELETE /apiops/settings/ai-topic-category-presets/{entryName}/

Authentication

Requires a Personal API Access Token with admin privileges.

Header

Authorization: Bearer YOUR_TOKEN

Request

Path Parameters

Parameter	Type	Required	Description
entryName	string	Yes	Name of the entry to delete (case-insensitive)

Query Parameters

Parameter	Type	Required	Default	Description
projectId	string	No	admin	Scope project id. Omit for the admin/global scope.

Response

Success Response (200 OK)

{
  "status": "SUCCESS"
}

Error Response (400 Bad Request)

{
  "status": "FAILURE",
  "resultMessage": "AI Content-Safety Category (name: insider-data-exfiltration) was not found!"
}

Error Response (401 Unauthorized)

{
  "status": "FAILURE",
  "resultMessage": "Token is not valid!"
}

cURL Example

curl -X DELETE \
  "https://demo.apinizer.com/apiops/settings/ai-topic-category-presets/insider-data-exfiltration/" \
  -H "Authorization: Bearer YOUR_TOKEN"

Notes and Warnings

• Deleting a shipped entry is permanent: Mongock deduplicates changesets by id and no seed changeset is runAlways=true, so a seed that already ran does not run again — a deleted shipped category does not reappear on a version upgrade. It returns only if a future release ships an explicit re-seed changeset. If you only want to stop using the category without losing it, disable it instead of deleting it
• Identified by name, never by id
• Admin Only: a project-scoped AI_DEVELOPMENT token is not sufficient on this surface

Related Documentation

• List AI Content-Safety Categories - List all entries
• AI Content-Safety Categories API - Resource overview