Delete Model Catalog Entry

Endpoint

DELETE /apiops/projects/{projectName}/llm-models/{modelName}/

Authentication

Requires a Personal API Access Token.

Header

Authorization: Bearer YOUR_TOKEN

Request

Headers

Header	Value	Required
Authorization	Bearer {token}	Yes

Path Parameters

Parameter	Type	Required	Description
projectName	string	Yes	Project name
modelName	string	Yes	Model catalog entry name, in \{providerCode\}/\{modelId\} form (e.g. openai/gpt-5-mini)

Query Parameters

None

Response

Success Response (200 OK)

{
  "status": "SUCCESS",
  "deploymentResult": {
    "success": true
  }
}

Response Fields

Field	Type	Description
status	string	Response status: SUCCESS or FAILURE
deploymentResult	object	Result of the delete operation
deploymentResult.success	boolean	Whether the operation completed successfully

Error Response (400 Bad Request)

{
  "status": "FAILURE",
  "resultMessage": "Model catalog entry (name: openai/gpt-5-mini) was not found!"
}

or (attempting to delete a built-in model)

{
  "status": "FAILURE",
  "resultMessage": "Built-in model catalog entries are read-only through APIops."
}

Error Response (401 Unauthorized)

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

cURL Example

curl -X DELETE \
  "https://demo.apinizer.com/apiops/projects/MyProject/llm-models/openai%2Fgpt-5-mini/" \
  -H "Authorization: Bearer YOUR_TOKEN"

Notes and Warnings

• Built-in models cannot be deleted here: APIops is project-scoped while a built-in catalog row is installation-wide, so the request is rejected with 400. Only custom entries (builtIn=false) can be removed through this API. A System Administrator can delete a built-in row from the admin UI — see Model Catalog; that deletion is permanent, because a version upgrade only seeds models that are missing and does not restore one you removed on purpose.
• Project ownership: The entry must belong to the named project. Attempting to delete an entry owned by another project is blocked (cross-project delete guard).
• Name form: The catalog name uses the {providerCode}/{modelId} format. URL-encode the / as %2F in the path.
• Not found: Deleting a name that does not exist in the project returns a 400 with a "was not found" message.

Related Documentation

• Update Model Catalog Entry - Update an existing entry
• List Model Catalog Entries - List all entries in a project
• Model Catalog API - Resource overview
• Authentication Guide - How to obtain and use API tokens
• Error Handling - Error response formats