The following table describes the errors that you might encounter, and the corresponding causes for the errors. Apigee Integration uses the canonical error codes defined in google.rpc.Code.
For information about Apigee Integration errors and different error handling strategies, see Errors and error handling.
| Standard exception type | Canonical code | HTTP code | Description |
|---|---|---|---|
| FailedPreconditionException | FAILED_PRECONDITION |
400 | Request can not be executed in the current system state. |
| BadRequestException | INVALID_ARGUMENT |
400 | Client specified an invalid argument. Check error message and error details for more information. |
| UnauthenticatedException | UNAUTHENTICATED |
401 | Request not authenticated due to missing, invalid, or expired OAuth token. |
| ForbiddenException | PERMISSION_DENIED |
403 | Client does not have sufficient permission. This can happen if the OAuth token doesn't have the right scopes, the client doesn't have the required permissions, or the API has not been enabled. |
| NotFoundException | NOT_FOUND |
404 | A specified resource is not found. |
| AlreadyExistsException | ALREADY_EXISTS |
409 | The resource that a client tried to create already exists. |
| InternalError | INTERNAL |
500 | Internal server error. Typically a server bug. This can happen if any of the tasks or triggers are incorrectly configured. |
| UnimplementedException | UNIMPLEMENTED |
501 | API method not implemented by the server. |
| ServiceUnavailableException | UNAVAILABLE |
503 | Service unavailable. Typically the server is down. |
| AbortedException | ABORTED |
409 | Response size is too large. |