Reference
Errors and rate limits
REST errors use this envelope. Keep the request ID for support and never log your API key: { "error": { "code", "message", "requestId" } }
| Code | HTTP | Meaning |
|---|---|---|
| BAD_REQUEST | 400 / 409 | HTTP 400 means the request body is invalid; HTTP 409 means the upload cannot be completed in its current state. |
| UNAUTHORIZED | 401 | The API key is missing, invalid, or revoked. |
| PAID_PLAN_REQUIRED | 403 | The account does not have an eligible paid plan. |
| INSUFFICIENT_SCOPE | 403 | The API key does not include the required scope. |
| NOT_FOUND | 404 | The owned upload, file, or share was not found. |
| UPLOAD_NOT_READY | 409 | The uploaded object is not ready for completion. |
| FILE_TOO_LARGE | 413 | The file exceeds the applicable size limit. |
| OBJECT_VALIDATION_FAILED | 422 | The uploaded object failed validation. |
| QUOTA_EXCEEDED | 429 | The upload quota is exhausted. |
| RATE_LIMIT_EXCEEDED | 429 | The API request rate is exhausted. |
| SERVICE_UNAVAILABLE | 503 | A required service is temporarily unavailable. |
Rate-limit headers
Rate-limit headers are returned only on 429 responses: X-RateLimit-Limit, X-RateLimit-Remaining, Retry-After.