Errors & Rate Limits
All public endpoints return one of three shapes—object, list, or error—and expose request IDs and rate-limit data in headers.
Response Model
Single-resource endpoints return an object directly, such as monitoring.job.
List endpoints return { object: "list", data: [...] }.
Errors return { error: { code, message, request_id, details? } }.
1{2"error": {3"code": "INVALID_ARGUMENT",4"message": "请求参数无效",5"request_id": "req_01ht2error",6"details": {7"fieldErrors": {8"subreddit": [9"Required"10]11}12}13}14}
Response Headers
A unique ID for each request, used for debugging and log correlation.
The total quota for the current token within the rate-limit window.
The remaining quota in the current window.
The reset time for the current window (Unix timestamp in seconds).
Suggested wait time in seconds when rate limited.
Common Error Codes
- UNAUTHORIZED: missing or invalid token.
- FORBIDDEN: the token exists but lacks the required scope.
- INVALID_ARGUMENT: the body, query, or path parameters are invalid.
- NOT_FOUND: the resource does not exist or does not belong to the current account.
- RATE_LIMITED: the current token is calling too frequently.
- RESULT_NOT_READY：异步任务还没产出结果。
Machine-readable error code.
Human-readable error description.
Request ID for this call.
Additional details for validation failures and similar cases.