How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Vital lab_tests API

The lab_tests API from Vital — 9 operation(s) for lab_tests.

Vital lab_tests API is one of 18 APIs that Vital publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 7 JSON Schema definitions.

Tagged areas include Lab Tests. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and 7 JSON Schemas.

This API exposes 11 operations across 9 paths, and defines 23 schemas. It is described by OpenAPI 3.1.0, at version 0.4.497.

Requests are made against 4 base URLs: https://api.us.junction.com, https://api.eu.junction.com, https://api.sandbox.us.junction.com, https://api.sandbox.eu.junction.com.

11 operations 9 paths 23 schemas 8 GET1 PATCH2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
0.4.497
Base URL
https://api.us.junction.com
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Vital lab_tests API declares 1 security scheme for authenticating requests. An API key is passed in the header as x-vital-api-key (apiKeyAuth). By default, every request must be authenticated.

  • apiKeyAuth — Vital Team API Key

Paths & Operations 11

Across 9 paths, the API surfaces 11 operations — 8 GET, 1 PATCH, 2 POST. Each is listed below with its method, path, parameters, and response codes.

lab_tests 11
GET
/v3/lab_testsdeprecated
Get Lab Tests For Team
get_lab_tests_for_team_v3_lab_tests_get 9 params → 200422
POST
/v3/lab_tests
Create Lab Test For Team
create_lab_test_for_team_v3_lab_tests_post body → 200422
PATCH
/v3/lab_tests/{lab_test_id}
Update Lab Test For Team
update_lab_test_for_team_v3_lab_tests__lab_test_id__patch 1 param body → 200422
GET
/v3/lab_tests/{lab_test_id}
Get Lab Test For Team
get_lab_test_for_team_v3_lab_tests__lab_test_id__get 2 params → 200422
GET
/v3/lab_tests/markers
Get Markers
get_markers_v3_lab_tests_markers_get 7 params → 200422
POST
/v3/lab_tests/list_order_set_markers
Get Markers For Order Set
get_markers_for_order_set_v3_lab_tests_list_order_set_markers_post 2 params body → 200422
GET
/v3/lab_tests/{lab_test_id}/markers
Get Markers For Test
get_markers_for_test_v3_lab_tests__lab_test_id__markers_get 4 params → 200422
GET
/v3/lab_tests/{lab_id}/markers/{provider_id}
Get Markers By Provider Id
get_markers_by_provider_id_v3_lab_tests__lab_id__markers__provider_id__get 3 params → 200422
GET
/v3/lab_tests/labs
Get Labs
get_labs_v3_lab_tests_labs_get → 200
GET
/v3/lab_test
Get Paginated Lab Tests For Team
get_paginated_lab_tests_for_team_v3_lab_test_get 11 params → 200422
GET
/v3/lab_test/{lab_test_id}/collection_instruction_pdf
Get Lab Test Collection Instructions Url
get_lab_test_collection_instructions_url_v3_lab_test__lab_test_id__collection_instruction_pdf_get 1 param → 200422

Schemas 23

The contract defines 23 schemas that model the data the API accepts and returns. The most detailed are ClientFacingLabTest (16 properties), ClientFacingMarkerComplete (15 properties), ClientFacingMarker (14 properties), Question (9 properties). Each schema is shown below with its type and property counts.

Question
object
9 properties 7 required
ClientFacingLoinc
object
5 properties 4 required
GetMarkersResponse
object
5 properties 5 required
Labs
string
ℹ️ This enum is non-exhaustive.
MarkerType
string
ℹ️ This enum is non-exhaustive.
LabTestStatus
string
ℹ️ This enum is non-exhaustive.
ClientFacingLab
object
8 properties 8 required
CreateLabTestRequest
object
8 properties 3 required
HTTPValidationError
object
1 property
ClientFacingMarkerComplete
object
15 properties 4 required
LabTestGenerationMethodFilter
string
ℹ️ This enum is non-exhaustive.
ClientFacingLabTest
object
16 properties 10 required
ClientFacingMarker
object
14 properties 3 required
LabTestCollectionMethod
string
The method used to perform a lab test. ℹ️ This enum is non-exhaustive.
AoE
object
1 property 1 required
UpdateLabTestRequest
object
2 properties
LabTestSampleType
string
The type of sample used to perform a lab test. ℹ️ This enum is non-exhaustive.
Answer
object
3 properties 3 required
OrderSetRequest
object
3 properties
AddOnOrder
object
2 properties
QuestionType
string
ℹ️ This enum is non-exhaustive.
LabTestResourcesResponse
object
2 properties 2 required
ClientFacingResult
object
7 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

vital-io-lab-tests-api-openapi.yml Raw ↑

Other APIs Vital publishes across the network.

Vital Management API
Vital Aggregate API
Vital compendium API
Vital insurance API
Vital introspect API
Vital lab_account API
Vital lab_report API
Vital link API
Vital order API
Vital order_transaction API
Vital orders API
Vital payor API
Where this information came from

This is an independent, third-party profile of Vital lab_tests API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.