When your receive a callback from the fax api notifying you of a failure, it will contain two values that can help you understand what went wrong: an errorCode and an type.
The type will give you a general idea of why the operation failed, whereas the errorCode describes the issue in more detail. Below we list the error_codes for the API, segmented by their corresponding error_type.
errorType | string Type of error for the Document conversion | ||||||||||||||||||||||
errorMessage | string The error message | ||||||||||||||||||||||
errorCode | integer The error code returned during document conversion.
|
{- "errorType": "DOCUMENT_CONVERSION_ERROR",
- "errorMessage": "There was a problem in converting and merging files to the output file format. Contact support.",
- "errorCode": 4
}
Request errors are returned as HTTP status codes. The following table lists the possible error codes and their meaning.
The type will give you a general idea of why the operation failed, whereas the errorCode describes the issue in more detail. Below we list the error_codes for the API, segmented by their corresponding error_type.
{
"code": "404",
"error": "Bad Request",
"message": "
The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications.
It could be invalid JSON, missing required fields, or other issues."
}
Empty body, or you have the wrong API key, secret, or project.
{
"code": "402",
"error": "Payment required",
"message": "You have reached 0 balance on your account please make a payment."
}
{
"code": "404",
"error": "Not found",
"message": "The resource is not found, not available, or does not exist."
}
{
"code": "422",
"error": "Invalid parameters",
"message": "The request could not be understood by the server due to malformed syntax.
The client SHOULD NOT repeat the request without modifications."
details: {
fieldViolations: [
{
field: "to",
description: "The (+15551) is not a valid phone number"
}
]
}
Rate limit exceeded, please back off and try again later. If you need higher rate please contact support.
Probably no body, but if there is a body it will look like this:
{
"code": "500",
"error": "Internal service error",
"message": "Most likely a temporary issue, please try again later. If the problem persists, please back of on this request and contact support."
}
This non-http code will be used when there is an issue connecting to the designated callback URL. The response will look like this:
{
"error": "Could not connect to URL: https://123.456.789.00"
}
Please note that the response code is probably the most important part of the response, but the error object will contain more information about the error.
Not all errors return this object, and the details
object is not always present.
code | integer <int32> HTTP status code or error code |
status | string Response status name. |
message | string A developer-facing error message |
Array of objects Details of the errors |
{- "code": 400,
- "status": "INVALID_ARGUMENT",
- "message": "Bad request.",
- "details": [
- {
- "type": "NOT_FOUND"
}
]
}