Delete an LLM backend through the root-level API¶
Delete an LLM backend and its endpoints.
DELETE https://api.moi.matrixorigin.cn/v5/llm/backends/{backend_id}
Before you call this API¶
Set BASE_URL to the product API prefix https://api.moi.matrixorigin.cn/v5. For private deployments, use the corresponding product API URL.
Configure identity, Workspace, and object permissions in the same environment.
Request¶
curl --request DELETE \
"$BASE_URL/llm/backends/$BACKEND_ID" \
--header "X-API-Key: $MOI_KEY" \
--header "X-Workspace-ID: $WORKSPACE_ID"
Parameter |
Location |
Type |
Required |
Description |
|---|---|---|---|---|
|
Headers |
string |
Yes |
Workspace ID in the same environment. |
|
Path |
integer |
Yes |
Positive ID returned by an earlier read. |
Requires object model_backend.delete. Backend and endpoint deletion outcomes depend on the transaction and IAM lifecycle together. DAO handling of missing rows is not a public idempotency guarantee.
Successful response¶
{
"code": "OK",
"msg": "OK",
"data": {
"success": true
}
}
HTTP 200。
Field |
Type |
Description |
|---|---|---|
|
string |
OK on success. |
|
string |
OK on success. |
|
object |
Error responses¶
Errors and result confirmation distinguishes the two protocols. Parse omitted fields, SDK zero values, and empty HTTP responses separately. Confirm writes using the corresponding read operation.