Status API

Check the status of the text extraction process. This can be used to check the status of the conversion process when the conversion is done in async mode.

Endpoint	/whisper-status
URL	https://llmwhisperer-api.us-central.unstract.com/api/v2/whisper-status
Method	GET
Headers	unstract-key: <YOUR API KEY>

Parameters

Parameter	Type	Default	Required	Description
whisper_hash	string		Yes	The whisper hash returned while starting the whisper process.

Example Curl Request

curl -X GET --location 'https://llmwhisperer-api.us-central.unstract.com/api/v2/whisper-status?whisper_hash=XXXXXXXXXXXXXXXXXXX' \
-H 'unstract-key: <Your API Key>'

info

To include the headers in the response use curl -i in the request.

Response

HTTP Status	Content-Type	Headers	Description
200	application/json		The API will return a JSON with the status. Refer below for JSON format
400	application/json		The API will return a JSON with the error message. Refer below for JSON format

Example 200 Response

{
    "status": "processing"
}

Possible Statuses

200 OK

• accepted: The document has been accepted and has been added to the processing queue.
• processing: The document is still being processed. Check back later.
• stage_*: The page pipeline has been created. Current stage of processing
• processed: The document has been processed and the text is ready to be retrieved.
• delivered: The text has been retrieved. (deprecated)
• failed: The document processing has failed. Check the error message for more details.
• unknown: The whisper hash is not valid. Check the hash and try again.
• webhook_retries_exceeded: The webhook retries have been exceeded. The webhook will not be called again. But available for manual retrieval.

400 Bad Request

• error_*: The error message.
• retrieved: The text has already been retrieved. The text is deleted once it is retrieved. This behaviour is security feature to make sure that we do not persist the text after it is retrieved. This can be overridden in on-prem installations.