Developers
API errors
Handle gRPC failures and billing error details.
Check the gRPC status and message before retrying.
| Status / message | Response |
|---|---|
UNAUTHENTICATED | Check authentication and replace invalid or revoked keys. |
PERMISSION_DENIED | Check scopes and your plan's API access on the Pricing page. |
RESOURCE_EXHAUSTED / rate limit exceeded | Retry after the seconds specified by the retry-after trailer. |
RESOURCE_EXHAUSTED / too many active event streams | Close unused streams. |
RESOURCE_EXHAUSTED / too many pending requests | Let in-flight calls finish before retrying. |
Billing failures
ErrorDetail.code starts with billing_ for billing rejections; the response preserves the billing message. Budget and plan-cap failures return RESOURCE_EXHAUSTED; plan-feature and inactive-account failures return PERMISSION_DENIED.
Before resubmitting, check the budget and your plan's limits on the Pricing page. Follow command retry rules when retrying submissions.