Confirm Blood Draw

Use this guide to confirm that a blood draw has taken place. Confirmation records the lab codes (tube barcodes) of the physical kit and triggers the lab order pipeline; result progress is then read from Get Results.

Confirmation is irreversible. Once you confirm a blood draw, no further modifications — including adding panels — can be made to the appointment. Make sure all panels are attached and all details are correct before proceeding.

Ensure panels are added

Before confirming, verify that all necessary test panels have been added to the appointment. You cannot add panels after confirmation.Review the Schedule an Appointment guide for instructions on attaching panels.Confirm the following before continuing:

All required panels are attached to the appointment.
The profile_id and location_id on the appointment are correct.
The patient has completed the blood draw and the barcode of every tube is at hand.

Confirm the blood draw

Send a POST request to /api/v1/appointments/{id}/confirm with the lab codes from the physical blood draw kit. A venous draw has one code printed on every tube — send it as lab_code. A pharmacy draw has one code per panel — send them as lab_codes, one entry per code with the panel_ids it covers (from the appointment’s panels); each panel becomes its own laboratory requisition under its code.

Each code must be the numeric string printed on the physical tube handed to the patient. Do not substitute a different identifier — an incorrect code will cause the lab order to fail. Every code is validated before anything is written; if one is rejected, nothing is recorded.

curl --request POST \
  --url https://anivahealth.com/api/v1/appointments/c9d4e827-3b6f-4a1c-8d2e-5f0b9c7e3a12/confirm \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "lab_code": "7642001234"
  }'

curl --request POST \
  --url https://anivahealth.com/api/v1/appointments/c9d4e827-3b6f-4a1c-8d2e-5f0b9c7e3a12/confirm \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "lab_codes": [
      { "lab_code": "7642001234", "panel_ids": ["f1c2d4a3-7b8e-4f2a-9c1d-2e3f4a5b6c7d"] },
      { "lab_code": "7642001235", "panel_ids": ["0a9b8c7d-6e5f-4a3b-2c1d-0e9f8a7b6c5d"] }
    ]
  }'

const response = await fetch(
  'https://anivahealth.com/api/v1/appointments/c9d4e827-3b6f-4a1c-8d2e-5f0b9c7e3a12/confirm',
  {
    method: 'POST',
    headers: {
      'Content-Type': 'application/json',
      'x-api-key': 'YOUR_API_KEY',
    },
    body: JSON.stringify({
      lab_codes: [
        { lab_code: '7642001234', panel_ids: ['f1c2d4a3-7b8e-4f2a-9c1d-2e3f4a5b6c7d'] },
        { lab_code: '7642001235', panel_ids: ['0a9b8c7d-6e5f-4a3b-2c1d-0e9f8a7b6c5d'] },
      ],
    }),
  }
);

const result = await response.json();

A successful request returns 200 OK:

{
  "success": true
}

Verify appointment status

After confirmation, retrieve the appointment to verify its status has changed to blood_drawn.

curl --request GET \
  --url https://anivahealth.com/api/v1/appointments/c9d4e827-3b6f-4a1c-8d2e-5f0b9c7e3a12 \
  --header 'x-api-key: YOUR_API_KEY'

const response = await fetch(
  'https://anivahealth.com/api/v1/appointments/c9d4e827-3b6f-4a1c-8d2e-5f0b9c7e3a12',
  {
    headers: {
      'x-api-key': 'YOUR_API_KEY',
    },
  }
);

const appointment = await response.json();
console.log(appointment.status); // "blood_drawn"

Once the appointment shows status: "blood_drawn", the lab order pipeline has been triggered. The appointment status itself stays at blood_drawn from here on; finer-grained downstream progression is exposed via dedicated endpoints: follow each entry in the inline shipments array to Get Shipment for courier in-transit / delivered events, and use Get Results for lab result completion (status: "in_progress" → "completed").

What happens next

After confirmation, Aniva’s lab order pipeline takes over:

Each lab code is matched to its physical tubes at the lab — every panel’s requisition carries the code on its own tubes.
The panels attached to the appointment determine which tests are run.
When results are ready they’re associated with the patient profile and surface in Get Results — the response’s top-level status field flips from in_progress to completed once every submission has arrived.

No further action is required from your integration after confirmation.

Error handling

Status	Cause	Resolution
`400 Bad Request`	Neither or both of `lab_code` / `lab_codes` given, a code is non-numeric, or a code or panel is repeated.	Send exactly one of the two, with the exact numeric codes from the physical tubes.
`409 Conflict`	A code cannot be used (already assigned, unregistered, belongs to a home kit, wrong clinic), a panel has no code, or the appointment is not confirmable.	Read `reason` and `lab_code`; scan a different tube or check the appointment status.
`403 Forbidden`	Your API key does not have access to this operation.	Contact Aniva to confirm your API key permissions.
`404 Not Found`	The appointment ID does not exist or does not belong to your account.	Verify the appointment ID is correct.

Get Started

Core Concepts

Guides

Confirm Blood Draw

What happens next

Error handling

​What happens next

​Error handling

What happens next

Error handling