Update 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) — no RLCL is updated, 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

PUT /apiops/projects/{projectName}/rlcl/{rlclName}/

Authentication

Requires a Personal API Access Token.

Header

Authorization: Bearer YOUR_TOKEN

Request

Headers

Header	Value	Required
Authorization	Bearer {token}	Yes
Content-Type	application/json	Yes

Path Parameters

Parameter	Type	Required	Description
projectName	string	Yes	Project name
rlclName	string	Yes	RLCL name (cannot be changed)

Request Body

Same structure as Create RLCL. See Create RLCL for field descriptions, including identitySource, targetAudienceRuleList, outOfTargetAction and the generalQuota* fields.

Important Notes

• name must match the RLCL name in path (cannot be changed)
• All other fields can be updated
• Only the fields present in the request body are changed; omitted fields keep their current value
• When provided, targetAudienceRuleList replaces the whole existing list
• When identitySource is AUTH_RESOLVED, executionOrder is forced to AFTER_API_METHOD and targetVariable is ignored
• When outOfTargetAction is GENERAL_QUOTA, generalQuotaPermittedMessageCount and generalQuotaTimeIntervalPeriodLength must be greater than 0 and generalQuotaTimeInterval is required
• Credentials and endpoints are not updated by this endpoint

Response

Error Response — Retired (400 Bad Request)

{
  "status": "FAILURE",
  "resultMessage": "Legacy rate limit lists are retired; they were migrated to limit plans and assignments and are no longer enforced."
}

credentialRateLimit.retired — Legacy rate limit lists are retired: they were migrated to limit plans and assignments at upgrade and are no longer enforced by the gateway. Manage limits from the Limits screen; this list is kept read-only for audit.

This is now the only response this endpoint returns. The success and validation-error responses below no longer occur; they are kept for historical reference.

Success Response (200 OK)

{
  "status": "SUCCESS",
  "deploymentResult": {
    "success": true
  }
}

Error Response (400 Bad Request)

{
  "status": "FAILURE",
  "resultMessage": "RLCL (PremiumUserRLCL) is not found!"
}

cURL Example

curl -X PUT \
  "https://demo.apinizer.com/apiops/projects/MyProject/rlcl/PremiumUserRLCL/" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "description": "Updated rate limit for premium users",
    "enabled": true,
    "executionOrder": "BEFORE_API_PROXY",
    "cacheConnectionTimeoutInSeconds": 5,
    "cacheErrorHandlingType": "CONTINUE",
    "timeIntervalWindowType": "SLIDING",
    "showRateLimitStatisticsInResponseHeader": true
  }'

Permissions

• User must have IDENTITY + MANAGE permission in the project

Notes and Warnings

• Name Cannot Change:
  • Name is used as identifier and cannot be changed
  • Use the existing name in the request
• Credentials/Endpoints:
  • Credentials and endpoints are not updated by this endpoint
  • Use separate endpoints for managing credentials and endpoints

Related Documentation

• Create RLCL - Create a new RLCL
• Delete RLCL - Delete an RLCL