Ana içeriğe geç

Delete Model Catalog Entry

Endpoint

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

Authentication

Requires a Personal API Access Token.

Authorization: Bearer YOUR_TOKEN

Request

Headers

HeaderValueRequired
AuthorizationBearer {token}Yes

Path Parameters

ParameterTypeRequiredDescription
projectNamestringYesProject name
modelNamestringYesModel 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

FieldTypeDescription
statusstringResponse status: SUCCESS or FAILURE
deploymentResultobjectResult of the delete operation
deploymentResult.successbooleanWhether 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 models cannot be deleted"
}

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 are protected: Entries with builtIn=true are read-only and can never be deleted — the request is rejected with 400. Only custom entries (builtIn=false) can be removed.
  • 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.