API reference
/v1/cc-rule-groups2 operations
← All groups · First call? Read the tutorial: auth, permissions, requests and responses, common failures
| Method | Path | Summary | Auth |
|---|---|---|---|
| GET | /v1/cc-rule-groups | — | Session |
| GET | /v1/cc-rule-groups/summary | CC rule group pill counts over every group | Session |
Contract file：api/control-openresty-security.openapi.yaml
/v1/cc-rule-groups| Status | Description |
|---|---|
200 | System groups are identified by system_rule_key, falling back to system_rule_id for legacy projections. Custom policy groups retain their UUID IDs. |
401 | Authentication required |
403 | Permission denied |
401 Check the credential format and whether it expired or was rotated.403 Check the key scopes, the owner’s current permissions and the tenant scope; never switch to a more privileged account./v1/cc-rule-groups/summaryCC rule group pill counts over every group
System groups count from the signed rule catalog once it has synced, else from the per-tenant projection; custom groups are the scope's CC policies. visible/disabled are enabled/disabled groups of both kinds.
| Status | Description |
|---|---|
200 | Counts. Fields： |
401 | Authentication required |
403 | Permission denied |
401 Check the credential format and whether it expired or was rotated.403 Check the key scopes, the owner’s current permissions and the tenant scope; never switch to a more privileged account.