API Reference - Requisitions
Get requisition
Retrieve a requisition.
GET
Access to requisitioning is disabled by default. To enable it, talk to us and we’ll get you set up
Authorizations
Token-based authentication with required prefix "Token"
Path Parameters
The ID of the requisition to retrieve.
Response
200
application/json
The ID of the requisition.
Example:
"f0e5a607-5b52-4d7c-a3f2-c40772d41482"
The full barcode of the sample mailed to the lab. Must be globally unique.
Example:
"19742938328"
The account number submitted to the lab.
Example:
"1234567890"
The name of the lab that will process the sample.
Example:
"CRL"
The panel codes of the test being performed on the sample. We'll create these with you during onboarding.
Example:
["PANEL-123"]
The two letter code of the state where the sample was collected.
Example:
"OH"
Available options:
created
, approved
, denied
, delivered
, received
, extra_quality_checks
, resulted
, rejected
, delivery_exception
Example:
"resulted"
Example:
[
{
"event": "created",
"date": "2020-01-01T00:00:00Z"
},
{
"event": "approved",
"date": "2020-01-01T00:00:00Z"
},
{
"event": "delivered",
"date": "2020-01-02T00:00:00Z"
},
{
"event": "received",
"date": "2020-01-03T00:00:00Z"
},
{
"event": "extra_quality_checks",
"date": "2020-01-04T00:00:00Z"
},
{
"event": "resulted",
"date": "2020-01-05T00:00:00Z"
}
]
An optional set of values that can be passed through to specific labs.
Example:
{
"crl_slip_id": "1234567890",
"crl_tier3_account_number": "12345678"
}
An optional dictionary of key-value pairs stored with the requisition.
Example:
{ "some_key": "some_value" }
Example:
"2020-01-01T00:00:00Z"
Example:
"2020-01-01T00:00:00Z"