Status messages returned by the page API.
Status Message | Description |
---|---|
INITIATED | Once Verity has checked that the URL is properly formed and does not already exist in the database, the request is passed to the Verity classification systems and the status updates to INITIATED. |
PROCESSING | The Verity classification system is processing the text and images on the specified page. |
PROCESSED | The URL has been processed and the Verity analysis JSON is available. The analysis results have been stored. |
ERROR | Page processing has been attempted and failed. The page URL is recorded in the Error Cache for 1 hour. If another request to process the same URL is received within 1 hour, Verity will return an Error status (unless the ignoreCache flag is enabled). After 1 hour, the ERROR status is cleared and Verity will process a new request for the URL. Several different conditions may result in an ERROR status message:
|
NOT_SUPPORTED | The language of the page is not supported (see Language Support Grid ). This status message may also be returned if Verity is unable to process the requested website. |
INSUFFICIENT_CONTENT | Verity’s content extraction processes cannot extract sufficient relevant content from a page to adequately perform classification tasks across text and imagery. |
INVALID | The HTTP URL request may be malformed, for example:
Example Invalid Request: { "dataAvailable": false, "Status": "INVALID", "pageUrl": "://gg.invalid/1" "uuid": "73146868-8d77-4bf0-8e89-eeb9d8e04cb2" } |
Page URL Error Codes
Error codes returned by the page API.
Error Code
|
Description |
HTTP Status Code | Internal/Client Facing | Response Examples |
---|---|---|---|---|
INSUFFICIENT_CONTENT |
| 422 - Unprocessable Entity | -> Client facing. | |
PAGE_CONTENT_CLASSIFICATION_FAILED |
| 500 - Internal Server Error | -> Client facing. | |
TEXT_EXTRACTION_REQUEST_FAILED |
| 500 - Internal Server Error | -> Internal. -> Mapped to PAGE_CONTENT_CLASSIFICATION_FAILED | |
IMAGE_CLASSIFIACTION_REQUEST_FAILED |
| 500 - Internal Server Error | -> Internal. -> Mapped to PAGE_CONTENT_CLASSIFICATION_FAILED | |
TEXT_EXTRACTION_RESPONSE_NOT_SUPPORTED |
| 200 - OK | -> Internal. | |
TEXT_EXTRACTION_RESPONSE_INTERNAL_ERROR |
| 500 - Internal Server Error | -> Internal. -> Mapped to PAGE_CONTENT_CLASSIFICATION_FAILED | |
TEXT_EXTRACTION_RESPONSE_INTERNAL_UNKNOWN |
| 500 - Internal Server Error | -> Internal. -> Mapped to PAGE_CONTENT_CLASSIFICATION_FAILED | |
PAGE_CONTENT_EXTRACTION_FAILED_WITH_403_FORBIDDEN |
| 422 - Unprocessable Entity | -> Client facing. | |
PAGE_CONTENT_EXTRACTION_FAILED_WITH_404_NOT_FOUND |
| 422 - Unprocessable Entity | -> Client facing. | |
PAGE_CONTENT_EXTRACTION_FAILED_WITH_500_INTERNAL_SERVER_ERROR |
| 422 - Unprocessable Entity | -> Client facing. | |
PAGE_CONTENT_EXTRACTION_FAILED_WITH_4XX |
| 422 - Unprocessable Entity | -> Client facing. | |
PAGE_CONTENT_EXTRACTION_FAILED_WITH_5XX |
| 422 - Unprocessable Entity | -> Client facing. | |
PAGE_CONTENT_EXTRACTION_FAILED |
| 422 - Unprocessable Entity | -> Client facing. | |
URL_CANNOT_EXCEED_2048_BYTES |
| 400 - Bad (Invalid) request. | -> Client facing. | |
URL_MISSING_HTTP_PROTOCOL |
| 400 - Bad (Invalid) request. | -> Client facing. | |
URL_MUST_NOT_BE_EMPTY |
| 400 - Bad (Invalid) request. | -> Client facing. | |
URL_MALFORMED |
| 400 - Bad (Invalid) request. | -> Client facing. | |
URL_CANNOT_EXCEED_2048_BYTES |
| 400 - Bad (Invalid) request. | -> Client facing. |