Status Response Codes
Stay organized with collections
Save and categorize content based on your preferences.
The following status codes can be returned in HTTP responses.
| HTTP Code |
HTTP Description |
Notes |
| 2xx |
OK |
Not an error; returned on success. This should also be used for business logic failures
(e.g. booking_failure in
CreateBookingResponse
is populated) |
| 400 |
Bad Request |
Bad Request/Invalid Arguments (merchant, service, slot not found,
trying to book an invalid slot, cancelling a booking that never
existed). |
| 401 |
Unauthorized |
Unauthenticated (invalid credentials, retry login). The request does
not have valid authentication credentials for the operation. |
| 403 |
Forbidden |
Permission denied/forbidden (caller is known and rejected). This
response must not be used for rejections caused by exhausting some
resource (use Too Many Requests instead for those errors).
Forbidden must not be used if the caller can not be
identified (use Unauthorized instead for those errors). |
| 404 |
Not Found |
Not found (Resource not found, invalid url, including invalid RPCs) |
| 409 |
Conflict |
The operation was aborted, typically due to a concurrency issue such
as a sequencer check failure or transaction abort. |
| 429 |
Too Many Requests |
Some resource has been exhausted, perhaps a per-user quota, or perhaps
the entire file system is out of space. |
| 499 |
Client Closed Request |
The operation was cancelled, typically by the caller. |
| 500 |
Internal Server Error |
Internal errors. This means that some invariants expected by the
underlying system have been broken. This error code is reserved for
serious errors. |
| 501 |
Not Implemented |
The operation is not implemented or is not supported/enabled in this
service. |
| 503 |
Service Unavailable |
The service is currently unavailable. This is most likely a transient
condition, which can be corrected by retrying with a backoff. |
| 504 |
Gateway Timeout |
The deadline expired before the operation could complete. For
operations that change the state of the system, this error may be
returned even if the operation has completed successfully. For example,
a successful response from a server could have been delayed long enough
for the deadline to expire. |
Sometimes multiple error codes may apply. Services should return the most
specific error code that applies.
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 2025-05-20 UTC.
[null,null,["Last updated 2025-05-20 UTC."],[[["\u003cp\u003eHTTP status codes indicate the outcome of a request, ranging from success (2xx) to various error types.\u003c/p\u003e\n"],["\u003cp\u003eClient errors (4xx) signal issues like bad requests, authentication failures, or missing resources.\u003c/p\u003e\n"],["\u003cp\u003eServer errors (5xx) represent problems on the server side, such as internal errors or service unavailability.\u003c/p\u003e\n"],["\u003cp\u003eSpecific error codes provide detailed information about the nature of the problem, enabling appropriate action.\u003c/p\u003e\n"],["\u003cp\u003eWhen multiple error codes could apply, the most specific one should be used.\u003c/p\u003e\n"]]],["HTTP responses can include various status codes. Successful operations return a 2xx code. Client-side errors include 400 (Bad Request), 401 (Unauthorized), 403 (Forbidden), 404 (Not Found), 409 (Conflict), 429 (Too Many Requests), and 499 (Client Closed Request). Server-side errors are 500 (Internal Server Error), 501 (Not Implemented), 503 (Service Unavailable), and 504 (Gateway Timeout). The most specific error code should be returned when multiple codes apply.\n"],null,["# Status Response Codes\n\nThe following status codes can be returned in HTTP responses.\n\n| HTTP Code | HTTP Description | Notes |\n|-----------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 2xx | OK | Not an error; returned on success. This should also be used for business logic failures (e.g. `booking_failure` in [`CreateBookingResponse`](/actions-center/verticals/reservations/e2e/reference/booking-server-api-rest/e2e-methods/createbooking-method) is populated) |\n| 400 | Bad Request | Bad Request/Invalid Arguments (merchant, service, slot not found, trying to book an invalid slot, cancelling a booking that never existed). |\n| 401 | Unauthorized | Unauthenticated (invalid credentials, retry login). The request does not have valid authentication credentials for the operation. |\n| 403 | Forbidden | Permission denied/forbidden (caller is known and rejected). This response must not be used for rejections caused by exhausting some resource (use `Too Many Requests` instead for those errors). `Forbidden` must not be used if the caller can not be identified (use `Unauthorized` instead for those errors). |\n| 404 | Not Found | Not found (Resource not found, invalid url, including invalid RPCs) |\n| 409 | Conflict | The operation was aborted, typically due to a concurrency issue such as a sequencer check failure or transaction abort. |\n| 429 | Too Many Requests | Some resource has been exhausted, perhaps a per-user quota, or perhaps the entire file system is out of space. |\n| 499 | Client Closed Request | The operation was cancelled, typically by the caller. |\n| 500 | Internal Server Error | Internal errors. This means that some invariants expected by the underlying system have been broken. This error code is reserved for serious errors. |\n| 501 | Not Implemented | The operation is not implemented or is not supported/enabled in this service. |\n| 503 | Service Unavailable | The service is currently unavailable. This is most likely a transient condition, which can be corrected by retrying with a backoff. |\n| 504 | Gateway Timeout | The deadline expired before the operation could complete. For operations that change the state of the system, this error may be returned even if the operation has completed successfully. For example, a successful response from a server could have been delayed long enough for the deadline to expire. |\n\nSometimes multiple error codes may apply. Services should return the most\nspecific error code that applies."]]