Delete Condition from RLCL
Retired — always returns 400
This endpoint is retired. Every call now returns 400 Bad Request with resultMessage naming the retirement (error key credentialRateLimit.retired) — nothing is changed, regardless of the request body. Existing lists were migrated to typed Limit Plans and assignments at upgrade; see Legacy Limits Migrated at Upgrade. Manage limits from the Limits screen instead. List RLCLs, Get RLCL, and Delete RLCL are unaffected. The rest of this page documents the retired behavior for historical reference.
Endpoint
DELETE /apiops/projects/{projectName}/rlcl/{rlclName}/condition/
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 |
| rlclName | string | Yes | RLCL name |
Request Body
None.
Response
Success Response (200 OK)
{
"status": "SUCCESS",
"deploymentResult": {
"success": true
}
}
cURL Example
curl -X DELETE \
"https://demo.apinizer.com/apiops/projects/MyProject/rlcl/PremiumUserRLCL/condition/" \
-H "Authorization: Bearer YOUR_TOKEN"
Permissions
- User must have
IDENTITY+MANAGEpermission in the project
Notes and Warnings
- Default Condition Reset:
- All existing conditions are removed
- The RLCL is reset to the default condition (AND rule with empty conditionRuleList)
- After reset, RLCL is applied unconditionally (always)
- No condition evaluation is performed
- The default condition cannot be deleted; it is automatically restored
Related Documentation
- Add Condition - Add condition to RLCL
- Update Condition - Update condition in RLCL