DELETE deployment API

You can use this API to request the deletion of a specific deployment of a published model in MLz. When the dual control feature is enabled, this API does not immediately delete the deployment. Instead, it creates a delete request entry in the APPROVAL_REQUESTS table, allowing for audit tracking and approval workflows.

HTTP method and URI path

DELETE /v3/published_models/{published_model_id}/deployments/{deployment_id}
where:
  • modelId identifies the published model.
  • deployment_id identifies the specific deployment to be deleted.

Standard headers

Use the following standard HTTP header with this request:

Content-Type: application/json

Authorization: <Bearer token>

Required authorizations

The user ID associated with the token which is specified in the request header needs to be granted with one of the following roles:

  • sysadm
  • mladm
  • apiuser (only if the deployment was created by the user)

Behavior when Dual Control feature is enabled

If the Dual Control feature is enabled, the system creates a delete deployment request. The system administrator other than the requester must respond to this request before proceeding.

Expected response

On completion, the service returns an HTTP response, with a status code that indicates whether your request is completed:

  • 204 no content : The delete request was successfully created or the deployment was deleted.
  • 4xx or 5xx: Indicates an error occurred.