Blood Result Upload

Blood Result Upload, or BRU, lets you submit one or more blood result documents to InsideTracker for asynchronous processing. When processing publishes results, those results become structured biomarker data that can support recommendations, scores, Inner Age, and other User-facing experiences.

Start here for the shared BRU file upload, process submission, status, and webhook flow. Format-specific pages add source-preparation and User-experience guidance for each supported BRU path.

Where This Fits

Use BRU when a User already has blood result documents and your integration needs InsideTracker to process those documents in the background.

BRU is different from lab ordering. Use Lab Connect when your integration needs to order a new Quest or Mobile Blood Draw test. Other blood result submission workflows are covered in their own guides.

What You Need

Before implementing BRU, make sure your integration has:

• A linked InsideTracker customer record for your User.
• A customer-level token obtained through the agreed on-behalf-of flow.
• One or more supported blood result document files.
• A way to store uploadedFileId and processId values in your system.
• A webhook endpoint for event-driven updates, or a polling job that can call the process status endpoint.

Workflow

BRU is asynchronous. Your application uploads files first, then submits a process that tells InsideTracker which uploaded files should be processed together.

1. Collect or receive the User's blood result documents.
2. Upload each document separately to the temporary BRU file endpoint.
3. Store every returned uploadedFileId.
4. Submit a BRU process with the full uploadedFileIds list.
5. Store the returned processId.
6. Use the BRU terminal webhook or process status endpoint to track completion.
7. When the process reaches PUBLISHED, use the returned blood result identifiers in downstream blood result and output workflows.

API Flow

Step 1: Upload Each File

Upload each document separately:

POST /bru/customer/v1/files
Content-Type: multipart/form-data
Authorization: Bearer {customer_token}

Include one required multipart field:

Each successful upload returns 201 Created with an uploadedFileId.

{
  "uploadedFileId": "97395c45-160a-44e6-a6db-f76570e12f8f"
}

Store every returned uploadedFileId until you submit the BRU process.

File rules from the public API reference:

InsideTracker performs virus scanning on uploaded files. Infected files are rejected.

Common error responses are 400 for an invalid request, 401 for an unauthorized request, and 500 for an internal server error.

Step 2: Submit The BRU Process

Submit a process with the full list of file IDs returned by the upload step:

POST /bru/customer/v1/processes
Content-Type: application/json
Authorization: Bearer {customer_token}

{
  "uploadedFileIds": [
    "497f6eca-6276-4993-bfeb-53cbbbba6f08"
  ]
}

The process submission returns 202 Accepted with a processId and the current process state. Store the returned processId so your integration can correlate status responses and webhook events.

The response includes fields such as:

Common error responses are 400 for an invalid request, 401 for an unauthorized request, and 500 for an internal server error.

Step 3: Track Processing

Use webhooks for event-driven updates when possible. If you need the latest process state, or if you need to recover after a missed webhook, poll the process endpoint:

GET /bru/customer/v1/processes/{processId}
Authorization: Bearer {customer_token}

When a process is in a terminal state, the response may include bloodResults with published blood result legacy IDs.

Common status endpoint errors are 401 for an unauthorized request, 404 when the process is not found, and 500 for an internal server error.

Terminal States And Webhook Handling

The BRU terminal webhook is documented in the public API reference as:

POST /webhooks/bru-terminal

Use the webhook payload to correlate the completed process back to the User and submission in your system.

Terminal states:

Example terminal webhook payload:

{
  "timestamp": "2025-01-15T10:45:00Z",
  "processId": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
  "extId": "6fa85f64-5717-4562-b3fc-2c963f66afa6",
  "status": "PUBLISHED",
  "autoPublishResult": true,
  "validationMode": "AUTO",
  "bloodResults": [
    {
      "legacyId": 99
    }
  ]
}

Implementation Checklist

Related Topics

• OCR Blood Result Upload
• Webhooks
• Lab Connect
• Adding Profile Data