Delete Endpoints 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}/endpoints/
Authentication
Requires a Personal API Access Token.
Header
Authorization: Bearer YOUR_TOKEN
Request
Same structure as Add Endpoints. See Add Endpoints for field descriptions.
Important Notes
- Only the specified endpoints are removed
- Endpoints not in the RLCL are ignored (no error)
- Match is based on
apiProxyName,endpointName, andendpointHTTPMethod endpointIdis automatically resolved fromendpointNameandendpointHTTPMethod(not sent in request)
Response
Same as Add Endpoints. See Add Endpoints for response format.
cURL Example
curl -X DELETE \
"https://demo.apinizer.com/apiops/projects/MyProject/rlcl/PremiumUserRLCL/endpoints/" \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"endpointRateLimitList": [
{
"apiProxyName": "MyAPI",
"endpointName": "/users",
"endpointHTTPMethod": "GET"
}
]
}'
Permissions
- User must have
IDENTITY+MANAGEpermission in the project
Notes and Warnings
- Selective Removal:
- Only the specified endpoints are removed
- Other endpoints remain in the RLCL
- Match Criteria:
- Endpoints are matched by
apiProxyName,endpointName, andendpointHTTPMethod endpointIdis automatically resolved fromendpointNameandendpointHTTPMethod(not sent in request)
- Endpoints are matched by
Related Documentation
- Add Endpoints - Add endpoints to RLCL
- Update Endpoints - Replace all endpoints