# deleteQuarantineFilePath delete Quarantine file path Endpoint: DELETE /har/api/v1/v1/registry/{registry_ref}/quarantine Version: 1.0 Security: x-api-key ## Path parameters: - `registry_ref` (string, required) Reference to the scope in which the registry exists. Format depends on the scope: - Account-level: account_id/registry_name/+ - Organization-level: account_id/org_id/registry_name/+ - Project-level: account_id/org_id/project_id/registry_name/+ The /+ suffix is used internally to route scoped requests. It must be included exactly as shown in the URL. ## Query parameters: - `artifact` (string) Artifat - `version` (string) Version - `file_path` (string) filePath - `artifact_type` (string) artifact type. Enum: "model", "dataset" ## Response 200 fields (application/json): - `status` (string, required) Request processing status indicator Enum: "SUCCESS", "FAILURE", "ERROR" ## Response 400 fields (application/json): - `code` (string, required) The HTTP error code Example: "404" - `details` (object) Additional context and details about the error. May include field-specific validation errors or debugging information. Example: {"field":"registry_identifier","reason":"Registry does not exist in the specified project","value":"invalid-registry"} - `message` (string, required) Human-readable error message explaining what went wrong Example: "Registry not found" ## Response 401 fields (application/json): - `code` (string, required) The HTTP error code Example: "404" - `details` (object) Additional context and details about the error. May include field-specific validation errors or debugging information. Example: {"field":"registry_identifier","reason":"Registry does not exist in the specified project","value":"invalid-registry"} - `message` (string, required) Human-readable error message explaining what went wrong Example: "Registry not found" ## Response 403 fields (application/json): - `code` (string, required) The HTTP error code Example: "404" - `details` (object) Additional context and details about the error. May include field-specific validation errors or debugging information. Example: {"field":"registry_identifier","reason":"Registry does not exist in the specified project","value":"invalid-registry"} - `message` (string, required) Human-readable error message explaining what went wrong Example: "Registry not found" ## Response 500 fields (application/json): - `code` (string, required) The HTTP error code Example: "404" - `details` (object) Additional context and details about the error. May include field-specific validation errors or debugging information. Example: {"field":"registry_identifier","reason":"Registry does not exist in the specified project","value":"invalid-registry"} - `message` (string, required) Human-readable error message explaining what went wrong Example: "Registry not found"