Skip to main content
POST
Create retrieval with case and Requestor

Authorizations

Authorization
string
header
required

API key authentication. Use format: Authorization: Bearer tavrn_sk_live_...

Body

application/json
patient
object
required

Patient details. Supply as much as you know — many facilities verify identity against DOB, SSN last-4, or address before releasing records.

facility
object
required

Facility name and address when creating a request manually. Provide this object or a top-level facility_id. Optional phone and fax contacts may be absent on read.

auth_form
object
required

The signed HIPAA authorization PDF. Required.

requested_records
object[]
required

One or more record lines to request. Each line carries its own type, dates, requirements, and (for billing) deliverable format.

Minimum array length: 1
case_id
string
required

Existing case in your organization; mutually exclusive with case.

Pattern: ^[a-fA-F0-9]{24}$
Example:

"111111111111111111111111"

facility_id
string

Facility ID from GET /v2/facilities. Provide exactly one of facility_id or facility.

Minimum string length: 1
Example:

"facility_example"

service_start_date
string<date> | null

Default start of the service date range (YYYY-MM-DD). Inherited by any requested_records[] line that omits its own service_start_date.

Example:

"2024-03-15"

service_end_date
string<date> | null

Default end of the service date range (YYYY-MM-DD). Inherited by any requested_records[] line that omits its own. Set to null for ongoing care.

Example:

"2024-09-30"

notes
string | null

Free-text instructions for the team handling this request

Example:

"Please include any radiology read reports"

submitter_email
string<email> | null

Email of a user in your organization to attribute the request to. That user receives retrieval notifications for the request. Must match an existing user in your organization or the request is rejected with a 400 validation_error. If omitted, the request is attributed to the creator of the API key.

Example:

"jane.smith@example.com"

attachments
object[]

Optional supporting documents for the request — e.g., cover letters, patient ID copies, prior-auth attachments. Each entry references an uploaded file by upload_id.

requestor_id
string

Existing profile in your organization. Mutually exclusive with requestor. Omit both to keep the organization default.

Pattern: ^[a-fA-F0-9]{24}$
Example:

"111111111111111111111111"

requestor
object

Create a Requestor profile with this retrieval. Requires requestors:write and cannot be combined with requestor_id.

allow_duplicate
boolean | null

When duplicate detection is enabled, retry with true after reviewing a 409 duplicate_request_detected response to create despite the blocking matches. Omission or null does not override the check.

case
object

Create a case with this retrieval. Requires cases:write and cannot be combined with case_id.

Response

Retrieval request created

id
string
required
Example:

"rr_abc123"

order_number
string
required
Example:

"T-ABC-12345"

case_id
string
required
Example:

"case_abc123"

status
enum<string>
required
Available options:
received,
processing,
action_required,
completed,
cancelled
Example:

"received"

created_at
string<date-time>
required
Example:

"2025-02-01T12:50:00Z"

updated_at
string<date-time>
required
Example:

"2025-02-01T12:50:00Z"

requestor_id
string | null
required

Selected Requestor profile ID.

Pattern: ^[a-fA-F0-9]{24}$
Example:

"111111111111111111111111"