HTTP Status Codes
| Status | Meaning | Common Causes |
|---|---|---|
| 200 | Success | Request completed successfully |
| 400 | Bad Request | Invalid parameters or malformed request |
| 401 | Unauthorized | Missing or invalid API key |
| 402 | Payment Required | Insufficient quota for this operation |
| 403 | Forbidden | Valid auth but insufficient permissions |
| 404 | Not Found | Resource doesn’t exist |
| 429 | Too Many Requests | Rate limit exceeded |
| 500 | Internal Server Error | Server-side error |
Error Response
When a request fails, the API returns a structured error body alongside the HTTP status code. Theerror_code field identifies the specific error for programmatic handling:
Error Codes
| Error Code | Description |
|---|---|
NOT_FOUND | Resource not found |
DRIVE_ITEM_CONFLICT | Drive item name conflict, e.g. file or folder with the same name already exists |
INVALID_ARGUMENT | Invalid input: parameter validation, type mismatch, or malformed body |
CONNECTOR_NOT_LINKED | Third-party connector (WPS, Lark, etc.) not yet authorized |
STATE_NOT_READY | Resource exists but its current state does not allow the operation |
ACCESS_DENIED | Caller lacks permission to access the resource |
QUOTA_EXCEEDED | Quota or usage limit exceeded |
DOWNLOAD_NOT_SUPPORTED | The requested resource does not support download |
INTERNAL_ERROR | Unexpected server-side error |
Error Handling Best Practices
Retry Logic
Error Logging
Next Steps
Authentication
Learn about authentication
Rate Limits
Understand rate limiting