Lab Connect

Lab Connect lets you order InsideTracker-managed blood testing for a linked User. Use it when your integration needs to assign testing inventory, choose the collection method, activate the order, guide the User through sample collection, and track the workflow until Results are published for downstream outputs.

Lab Connect supports InsideTracker-managed lab testing for Users in the United States and Canada. Supported collection methods are Quest Patient Service Center (PSC) testing and Mobile Blood Draw (MBD).

Where This Fits

Use Lab Connect when the User needs a new blood test ordered through an InsideTracker-managed lab workflow.

For existing blood result documents, use Blood Result Upload. For structured marker values that your system already has, use Add Blood Result.

Collection Methods

Choose the blood collection method for each User based on the User's location and the desired collection experience.

Location determines whether MBD is required. Mobile Blood Draw is required for Users in Canada and for Users located in NY, NJ, RI, AZ, or HI. For Users in other supported states, you may choose either PSC or MBD based on the experience you want to offer.

InsideTracker configures your organization's inventory for your program. Select inventory based on the panel or product being ordered. Choose the collection method separately, based on the User's location and the experience you want to offer.

InsideTracker handles required backend approval for both PSC and Mobile Blood Draw orders. If critical Results are returned, the lab-ordering vendor contacts the User directly as part of the clinical review process. Organization-specific CX scripting for that outreach is configurable during implementation with InsideTracker.

Before You Begin

Identifier Notes

The Glossary defines shared terms such as Test, Order, Results, and Result ID. Lab Connect also has a few endpoint-specific identifiers that need careful handling because some current APIs use Blood Results language for lab-ordering steps. In this flow, testId and resultId are used interchangeably for the same underlying testing/result container.

Workflow

API operations are shown with the operation name followed by the method and path.

1. Confirm the User is in the United States or Canada.
2. Choose the collection method. Users in Canada or an MBD-required state must use Mobile Blood Draw. Users in other supported states may use either PSC or MBD.
3. Select and assign inventory for the intended testing panel with Assign an item to a customer (POST /enterprise/inventory/sa/v1/assignment).
4. Store the testId returned by assignment.
5. If activating immediately, use the returned testId for the activation step.
6. If activation happens later, or your application needs current Test state, retrieve User test/status metadata with Provides all blood results (GET /api/customer/v1/tests).
7. If your experience shows which biomarkers are included in the assigned panel, call Get available marker for a specific result (GET /api/customer/blood/results-upload/{resultId}/available-markers).
8. Activate the order with Activate blood result (POST /api/customer/blood/results/{resultId}/activate) or Activate mbd-order (POST /api/pages/orders/activateMbd).
9. Set collection-method-specific expectations for scheduling, preparation, collection, and review.
10. Continue tracking order state with the same User test/status endpoint and lab-ordering webhook events.
11. When Results are published, retrieve or refresh downstream blood result and output workflows.

Assigned Inventory

Use Inventory Management to check available inventory and assign the selected inventory item to the User. Lab Connect depends on assignment, but the full inventory workflow is covered in Inventory Management.

For Lab Connect, the important assignment effects are:

When an endpoint names the path value {resultId}, pass the assigned container identifier as that path value.

After assignment, your application can proceed directly to activation when it has the required identifier and User details. Use User test/status metadata when you need to recover the assigned Test later or display the current state.

User Test/Status Metadata

Use the User test/status endpoint when your application needs current Test state, activation identifiers, or fulfillment status:

GET /api/customer/v1/tests
Authorization: Bearer {customer_token}

The API Reference labels this operation Provides all blood results. In Lab Connect, use it as the User test/status endpoint for assigned and activated lab orders.

This endpoint reports the current state of the User's Tests. Use the returned state to decide what to display to the User or whether the next step in your workflow is available. Do not use the guide to infer the internal business rules that produced a state; use the API Reference for the complete response schema and field definitions.

Common uses include:

Treat unknown or new returned values as other or unknown so your application remains resilient.

Choose The Collection Method

Use location as the primary collection-method input:

After choosing the collection method, use the matching activation endpoint. Use the User test/status endpoint for current state readback, not as a substitute for the location-based collection-method rule above.

Recover Or Inspect The Assigned Test

If activation happens later or your application needs to recover the assigned Test, use the User test/status endpoint to match the assigned Test metadata for the User.

If inventory has been assigned to the User, the response can include the corresponding Test metadata. Store the returned identifier for activation and Result ID-specific marker checks. When an endpoint names the path value {resultId}, pass the assigned container identifier required by that endpoint.

To see which biomarkers are available for a specific inactive assigned record, call the Get available marker for a specific result operation:

GET /api/customer/blood/results-upload/{resultId}/available-markers
Authorization: Bearer {customer_token}

Use this endpoint before activation when your application needs to show or verify which biomarkers are included in the assigned panel.

Activation

Activation uses a customer-level token. Use the activation endpoint that matches the selected collection method.

Activation locks the assigned Test to the User and starts the InsideTracker-managed approval and lab-order creation process.

Standard activation:

POST /api/customer/blood/results/{resultId}/activate
Content-Type: application/json
Authorization: Bearer {customer_token}

{
  "address": {
    "stateAbbr": "MA",
    "countryId": 233,
    "city": "Boston",
    "street": "123 Main St",
    "apartment": "",
    "zipCode": "02124"
  },
  "contact": {
    "phone": "11111111111"
  },
  "bloodDrawLocation": {
    "countryId": 233,
    "stateAbbr": "MA"
  }
}

Mobile Blood Draw activation:

POST /api/pages/orders/activateMbd
Content-Type: application/json
Authorization: Bearer {customer_token}

{
  "testId": 563,
  "note": "Sample text",
  "phone": "+12223333333",
  "countryId": 233,
  "stateAbbr": "NY",
  "city": "New York",
  "street": "123 Main St",
  "apartment": "123",
  "zipCode": "12311",
  "firstName": "John",
  "lastName": "Doe"
}

Fulfillment Expectations

After activation, the fulfillment experience differs by collection method. Set clear expectations for the User so the blood draw is completed without support escalation.

Status And Events

Use the User test/status endpoint to track assigned or activated lab orders and build User-facing states from the metadata returned by that endpoint.

When isPublished=true, Results are available for downstream blood result and output workflows. The Blood Results API also includes All blood results (GET /api/customer/v1/blood/results) and Get specific blood result (GET /api/customer/v1/blood/results/{id}) for result retrieval.

Webhook events can help your application react to lab-ordering and result milestones:

Critical-result review is handled through InsideTracker's lab-ordering vendor. If your User experience requires organization-specific language for vendor outreach, align that scripting during implementation.

Implementation Checklist

Related API Reference

Related Topics

• Creating Users
• Authorization and Security
• Inventory Management
• Blood Result Upload
• Add Blood Result
• Webhooks