Overview
- Permission scope
warnings.read- Community feature
warnings- Content type
application/json
Authentication
Two headers are required
Send a current cl_live_… key as a Bearer token and the community’s Clan ID separately.
Authorization: Bearer YOUR_API_KEY
X-Clan-Id: COMMUNITY_IDThe key must be enabled, the community API master switch must be on, and the key must include warnings.read.
Parameters
| Name | Location | Type | Required | Constraints and description |
|---|---|---|---|---|
id | path | string | Yes | pattern ^(?:0|[1-9][0-9]*)$ · The warning's per-community sequential id. |
Error responses
| Status | When it is returned |
|---|---|
| 400 | The request was malformed or failed validation. |
| 401 | The API key is missing, malformed, or not recognised for this community. |
| 403 | The key is disabled, lacks the required permission, or the community's subscription or tier does not cover API access or this feature. |
| 404 | The requested resource does not exist. |
| 409 | The request conflicts with current state. |
| 429 | Rate limited. |
| 500 | Unexpected server error. |
Rate limits
This endpoint shares the API key’s configured request budget. A 429 response includes a Retry-After header and limit, remaining, and resetMs values in error.details. Wait for the indicated interval before retrying.
Related endpoints
Examples use placeholders. Never put an API key in source control, a Roblox place file, screenshots, or support messages.