The two most common reasons a Lab Data result does not arrive are a duplicate file and a missing or unreadable sample collection date and time. Lab Data sends no Data Webhook in either case.
After a document is submitted, Lab Data returns 200 OK with a document_id and processes the document asynchronously. The result arrives only through your Data Webhook: there is no endpoint to check the processing status. For the request and response codes, see the Lab Data documentation.
Common situations
Situation | Possible cause | What to do |
No Data Webhook arrives after a 200 OK response | The file has exactly the same content as a previous submission from your organization. | No action is needed if the document was already processed. Search your stored results by document_id. |
No Data Webhook arrives after a 200 OK response | The sample collection date or time is missing or not legible. | Verify the document and submit it again. If the issue persists, contact ROOK Support with the document_id. |
A biomarker from the document is missing in panels_array | The biomarker did not pass validation. | Look for it in rejected_biomarkers_array and check its reason_string. |
A biomarker has plausibility_flag: true | The value is unusual or inconsistent with a related biomarker. | Review the value against the original document before using it. |
400 Bad Request with Unsupported file type | The file content is not PDF, JPEG, or PNG. | Convert the file to one of the supported formats. |
403 Forbidden | The credentials do not match the client_uuid in the path, or Lab Data is not activated in this environment. |
When you contact ROOK Support about a document, always include the document_id returned at submission.
Duplicate documents
A document is identified as a duplicate when your organization submits a file with exactly the same content as a previous submission, even for a different user_id. Duplicates are not processed again and do not generate a new Data Webhook.
Go-live checklist
Before sending production traffic, verify that:
Lab Data is activated for your client_uuid in the environment you call, from your ROOK Portal or through the ROOK Support team. Sandbox and Production are activated separately.
Your backend sends requests with Basic authentication, using your client_uuid and secret_key.
The client_uuid in the URL path matches the client_uuid of your credentials.
Your backend sends requests as multipart/form-data, with both file and timezone.
Your backend handles every documented response code.
Your Data Webhook is registered, reachable over HTTPS, and routes data_structure: "lab_result_event".
You store the document_id of each submission to correlate it with the Data Webhook result.
You have tested PDF, JPEG, and PNG documents, and every document shows a legible sample collection date and time.