Partner API

One API for your diagnostic Programs.

Integrate once across approved laboratory Programs for catalog, serviceability, orders, collection, status, results and events.

No separate Solia network or API platform subscription for approved health companies during the initial offering.

Laboratory testing, collection, clinical and third-party costs are separately governed by each Program. Production access follows Program approval.

How Solia works

Architecture

  1. Your product

    Consumer experience

  2. Solia Partner API

    One standardized contract

  3. Approved Diagnostic Program

    Governing rules

  4. Laboratory / collection

    Connected supply

CatalogServiceabilitySubjectsOrdersCollectionStatusResultsEvents

Your product keeps its consumer experience and customer relationship. Each approved Program governs laboratory, collection, clinical and commercial rules.

One integration

Connect additional approved laboratory Programs without rebuilding the integration model.

Laboratory, collection, provider and third-party operating terms remain governed by each Program. Approved Programs also define clinical ordering and requisition requirements, including use of existing authorized providers or eligible clinical network services where supported.

Integration at a glance

Four stages, one contract.

  1. Catalog and serviceability

    Read available offerings and where each can be serviced.

  2. Subjects and orders

    Create subjects and submit orders. Safe retries use idempotency.

  3. Collection, status and acknowledgments

    Track collection and order status, including laboratory acknowledgments.

  4. Released results and signed events

    Retrieve released results and receive signed events (webhooks).

Every call is governed by Program-specific authorization. This is a conceptual outline; exact endpoints and payloads are in the Developer Docs.

Connect once. Work across approved Programs.

Discovery
Catalog · Serviceability
Identity
Subjects
Operations
Orders · Collection · Status · Events
Results
Normalized results · Result return

One result contract

Results normalized across approved Programs.

A standardized result contract reduces the need for a different result model for every laboratory. Available fields depend on the connected laboratory integration.

  • Analyte
  • Value
  • Units
  • Reference range
  • Flag
  • Status
  • Specimen
  • Laboratory
  • Dates
  • Report reference

Identity across the workflow

  1. Subject
  2. Order
  3. Specimen
  4. Laboratory accession
  5. Result

Mapping depends on the connected laboratory contract.

From integration planning to Production.

  1. Program

    Connect an approved laboratory Program.

  2. Test

    Validate the integration in the available Program-backed environment.

  3. Production

    Move to Production after Program and integration readiness are approved.

Sandbox or Program-backed test access is confirmed during onboarding; discovery does not provision credentials.

Developer resources

Launch checklist

  1. 01Create your Solia On Demand health-company account.
  2. 02Request an authorized Sandbox Program and credentials.
  3. 03Place a synthetic Program order.
  4. 04Validate results and signed events.
  5. 05Request Production approval separately.

Sandbox access requires approval; synthetic tests are not real laboratory orders. Live laboratory, collection and clinical service costs are governed by approved Programs.

Overview
Contract scope and concepts.
Authentication
Program-scoped credentials.
Orders
Subjects, orders and idempotency.
Results
Released, normalized results.
Webhooks
Signed event delivery.

Start building

Review the Partner API contract.