Error Handling
The following are the error codes you might get when using Alert Center API
along with explanation on how to interpret them and guidance on what to do when
you get them. Learn more.
| Error code |
Description |
Action |
| 400: Bad Request |
This error code is returned when there is an error in the input request. |
Check the request, make required changes to the request, and try again. |
| 401: Invalid Credentials |
The access token is invalid or expired. |
Refresh the access token and try again. |
| 404 |
The specified resource was not found. This would be thrown when the requested alert does not exist. |
|
| 409 |
The specified resource already exists. |
Get the resource, and if needed perform an update. |
| 500 |
An unexpected error happened while processing the request. |
Retry with exponential backoff. |
| 503 |
Rate limit exceeded. |
Retry with exponential backoff. |
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2024-12-19 UTC.
[null,null,["Last updated 2024-12-19 UTC."],[[["This page lists error codes you might encounter when using the Alert Center API, along with their descriptions and suggested actions."],["Error codes range from bad requests (400) to server errors (500) and include issues like invalid credentials and rate limiting."],["Each error code has a recommended action, such as checking the request or refreshing the access token, to help you resolve the issue."],["For unexpected errors (500) and rate limiting (503), retrying with exponential backoff is recommended."]]],["The Alert Center API uses several error codes: 400 indicates a bad request requiring corrections, 401 means the access token needs refreshing, 404 signifies a missing resource. 409 denotes a pre-existing resource requiring retrieval and potential update. 500 signifies an unexpected error, and 503 means the rate limit was exceeded; both necessitate retries using exponential backoff. Each error code offers specific actions for resolution.\n"]]
