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 Report API

The lab_report API from Vital — 2 operation(s) for lab_report.

This API exposes 2 operations across 2 paths, and defines 14 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

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.

2 operations 2 paths 14 schemas 1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 1

Vital Lab Report 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 2

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

lab_report 2
POST
/lab_report/v1/parser/job
Create Lab Report Parser Job
CreateLabReportParserJob body → 200422
GET
/lab_report/v1/parser/job/{job_id}
Get Lab Report Parser Job
get_lab_report_parser_job_lab_report_v1_parser_job__job_id__get 1 param → 200422

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are LabReportResult (15 properties), LabReportResult_2 (14 properties), ResultMetadata (8 properties), ParsingJob (6 properties). Each schema is shown below with its type and property counts.

HTTPValidationError
object
1 property
ParsingJobStatus
string
ℹ️ This enum is non-exhaustive.
ParsingJobFailureReason
string
Machine-readable failure reasons for parsing jobs. ℹ️ This enum is non-exhaustive.
ParsedLabReportData
object
2 properties 2 required
CreateLabReportParserJobBody
object
3 properties 2 required
ResultMetadata
object
8 properties
ParsingJob
object
6 properties 4 required
LabReportResultType
string
ℹ️ This enum is non-exhaustive.
Interpretation
string
ℹ️ This enum is non-exhaustive.
LoincMatch
object
5 properties 3 required
LabReportResult
object
15 properties 2 required
ParsingJobFailureReason_2
string
Machine-readable failure reasons for parsing jobs. ℹ️ This enum is non-exhaustive.
ParsingJob_2
object
6 properties 4 required
LabReportResult_2
object
14 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

vital-io-lab-report-api-openapi.yml Raw ↑
Where this information came from

This is an independent, third-party profile of Vital Lab Report 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.