Retrieve lab orders and results for a clinic via Digitail's labs integration endpoint
domain: documentation.digitail.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate and call GET https://developer.digitail.io/api/v1/integrations/labs/orders with a filter[clinic_id] query parameter
Parse each order's lab, file_case_id, vet_id, order_ext_id, and status fields, plus the ordered_tests array (code, name)
Check the details object's is_editable, has_requisition_form, and ordering_ui_url/result_url fields to determine what actions and links to surface to clinic staff
Once results are available, read the nested result object for reported_at, the result file (name/url), and per-test outcomes (result, unit, conclusion)
Stay within Digitail's documented rate limit of 200 requests per minute when polling for new orders/results
Known gotchas
The endpoint only accepts specific documented filters - passing an unsupported filter key returns an error naming the allowed filters
A 401 means the bearer token is missing/invalid/expired and a 403 means the token is valid but lacks permission for the resource - handle them differently rather than treating both as a retry-auth case
Exceeding 200 requests/minute returns a 429 rate-limit error; back off rather than retrying immediately
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?