Skip to content
J·BJon BishopFractional growth marketer

Business platforms · llms.txt file breakdown

Junction llms.txt

A directly retrieved Markdown index for Junction's documentation, with 135 links across 5 detected headings.

The actual file

Source Markdown

The saved llms.txt text, displayed as source. The file belongs to its publisher; the live endpoint may change.

Open saved text ↗

Showing the first 18000 characters. Load the complete file to read the remainder.

# Junction

## Home

- [Junction](https://docs.junction.com/home/welcome.md): Integrate 300+ wearables, streamline lab operations, and build your own lab testing experience spanning all 50 states – with a single API.
- [Quickstart](https://docs.junction.com/home/quickstart.md): Get started with the Junction API by setting up API keys, connecting a wearable device, and fetching your first health data in minutes.
- [Libraries](https://docs.junction.com/home/libraries.md): Browse all Junction client libraries and SDKs, including typed API bindings for Java, Go, TypeScript, and Python, plus mobile SDKs for iOS and Android.
- [Getting Support](https://docs.junction.com/home/getting-support.md): Contact Junction support via email or Slack, and learn what information to include when reporting issues for faster resolution.

## Core Platform

### Product Guides

#### Overview

- [Junction API](https://docs.junction.com/api-details/junction-api.md): Overview of the Junction API including production and sandbox environments, regional endpoints, authentication methods, and core API capabilities.
- [Rate Limiting](https://docs.junction.com/api-details/rate_limiting.md): Learn about Junction API rate limiting behavior, HTTP 429 and 503 responses under server load, and targeted limits on specific endpoints.
- [Regions](https://docs.junction.com/api-details/regions.md): Understand how Junction stores data regionally in either the US (HIPAA compliant) or EU (GDPR compliant), and how organizations span multiple regions.

#### Webhooks & Events

- [Introduction](https://docs.junction.com/webhooks/introduction.md): Introduction to Junction webhooks that push new data and connection lifecycle updates to your configured HTTP endpoints in real time.
- [Retry Policy](https://docs.junction.com/webhooks/retry-policy.md): Understand the Junction webhook retry schedule with exponential backoff across eight attempts, from immediate retry up to 10 hours between attempts.
- [Event Structure](https://docs.junction.com/webhooks/event-structure.md): Reference for the standard webhook event payload structure including event_type, data, team_id, user_id, and client_user_id fields.
- [Debugging](https://docs.junction.com/webhooks/debugging.md): Debug webhook events using the Junction Dashboard Webhooks section or the Svix API to inspect delivery history and retry failed events.

#### ETL Pipelines

- [ETL Pipelines](https://docs.junction.com/webhooks/etl-pipelines/overview.md): Use ETL Pipelines to stream Junction events to supported destinations over authenticated TLS as a scalable alternative to webhooks.
- [Google Cloud Pub/Sub](https://docs.junction.com/webhooks/etl-pipelines/google-cloud-pubsub.md): Stream Junction events to Google Cloud Pub/Sub as an ETL pipeline destination, with message attributes, compression, and ordering details.
- [RabbitMQ](https://docs.junction.com/webhooks/etl-pipelines/rabbitmq.md): Stream Junction events to RabbitMQ as an ETL pipeline destination, with details on message headers, routing keys, and compression behavior.
- [Azure Event Hubs](https://docs.junction.com/webhooks/etl-pipelines/azure-event-hubs.md): Stream Junction events to Azure Event Hubs as an ETL pipeline destination, with details on event structure, properties, and compression.

### API Reference

#### User Management

- [Create user](https://docs.junction.com/api-reference/user/create-user.md): Create or submit user via the Junction API. Requires authentication with your team API key.
- [Get User](https://docs.junction.com/api-reference/user/get-user.md): Retrieve user via the Junction API. Requires authentication with your team API key.
- [Get User by Client User ID](https://docs.junction.com/api-reference/user/resolve-user.md): Retrieve user resolve via the Junction API. Requires authentication with your team API key.
- [Update user](https://docs.junction.com/api-reference/user/patch-user.md): Partially update user via the Junction API. Requires authentication with your team API key.
- [Delete user](https://docs.junction.com/api-reference/user/delete-user.md): Remove user via the Junction API. Requires authentication with your team API key.
- [Undo User Deletion](https://docs.junction.com/api-reference/user/undo-delete-user.md): Create or submit user undo delete via the Junction API. Requires authentication with your team API key.
- [Get users](https://docs.junction.com/api-reference/user/get-users.md): Retrieve users via the Junction API. Requires authentication with your team API key.
- [Update User Demographics](https://docs.junction.com/api-reference/user/upsert-info.md): Partially update user info via the Junction API. Requires authentication with your team API key.
- [Get User Demographics](https://docs.junction.com/api-reference/user/get-info-latest.md): Retrieve user info latest via the Junction API. Requires authentication with your team API key.
- [Create user insurance](https://docs.junction.com/api-reference/user/create-insurance-beta.md): Create or submit user insurance via the Junction API. Requires authentication with your team API key.
- [Get latest insurance](https://docs.junction.com/api-reference/user/get-latest-insurance.md): Retrieve user insurance latest via the Junction API. Requires authentication with your team API key.

#### User Portal

- [Create Portal URL](https://docs.junction.com/api-reference/user/create-portal-url.md): Create a Portal URL for a user via the Junction API. Requires authentication with your team API key.

- [Lab Testing (130 pages)](https://docs.junction.com/_llms/lab-testing.txt): Documentation for Lab Testing.
- [Devices (300 pages)](https://docs.junction.com/_llms/devices.txt): Documentation for Devices.

## Junction Sense

### Product Guides

#### Junction Sense

- [Sense Overview](https://docs.junction.com/sense/overview.md): Junction Sense consolidates wearable data from multiple providers into tabular outputs with data prioritization, floating-time aggregation, and query APIs.
- [Continuous Query Overview](https://docs.junction.com/continuous-query-overview.md): Automatically transform connected-device data into structured datasets that update when data changes or a resource-specific schedule runs.
- [Using Continuous Query](https://docs.junction.com/sense/using-continuous-query.md): Create Continuous Queries in Junction Sense that evaluate automatically and push result changes via webhooks or ETL pipelines.
- [Device Reliability](https://docs.junction.com/sense/device-reliability.md): Monitor whether expected device data has been present for each user, so you can gauge how far to trust it as a foundation to build on.
- [Managing Queries](https://docs.junction.com/sense/managing-queries.md): Create, edit, and manage your Continuous Query configurations using the Junction Dashboard.
- [Source Prioritization](https://docs.junction.com/sense/data-prioritization.md): Learn how Junction Sense automatically prioritizes data from multiple providers and source types, keeping only the highest-priority source per group.
- [Using Query API](https://docs.junction.com/sense/using-query-api.md): Access the Junction Sense Query API through the Python SDK with DataFrame integration, the JSON API endpoint, or typed API bindings.
- [Query Use Cases](https://docs.junction.com/sense/examples.md): Explore practical code examples of Junction Sense Continuous Query use cases including daily sleep analysis, in both Python and JSON DSL.

#### Query DSL

- [Time and data semantics](https://docs.junction.com/sense/query-dsl/time-and-data-semantics.md): Understand how Junction Sense indexes records, creates local-time buckets, handles source corrections, and interprets summary and timeseries data.
- [Column expressions](https://docs.junction.com/sense/query-dsl/column-expressions.md): Reference for table column expressions in Junction Sense queries to select fields from activity, body, sleep, and timeseries resources.
- [SELECT clause](https://docs.junction.com/sense/query-dsl/select-clause.md): Use the SELECT clause in Junction Sense queries to choose table columns, apply aggregate functions, and retrieve group key columns.
- [GROUP BY clause](https://docs.junction.com/sense/query-dsl/group-by-clause.md): Use the GROUP BY clause in Junction Sense queries for date truncation, date part extraction, table column, and source column grouping.
- [WHERE clause](https://docs.junction.com/sense/query-dsl/where-clause.md): Use the WHERE clause in Junction Sense queries to filter summary or timeseries rows with SQL-style comparison and logical operators.
- [ALIGN clause](https://docs.junction.com/sense/query-dsl/align-clause.md): Use the ALIGN clause in Junction Sense queries to fill empty time buckets with carry-forward, carry-backward, or carry-nearest operators on sparse data.
- [List-column aggregation](https://docs.junction.com/sense/query-dsl/list-column-aggregation.md): Aggregate list columns in Junction Sense queries with a scalar-output subquery.
- [Sleep Macros](https://docs.junction.com/sense/query-dsl/sleep-analysis.md): Use value macro expressions for sleep analysis in Junction Sense queries to access computed sleep stage metrics and breakdowns.
- [Readiness Scores](https://docs.junction.com/sense/query-dsl/readiness-scores.md): Query daily recovery, stress, and strain scores from connected wearable providers using Junction Sense readiness score expressions.
- [Device Reliability](https://docs.junction.com/sense/query-dsl/device-reliability.md): Monitor daily wearable data presence by provider, source type, and resource with Junction Sense Continuous Query.

#### Python SDK

- [Getting Started](https://docs.junction.com/sense/python-sdk/getting-started.md): Get started with the Junction Sense Python SDK for authentication, query construction, and integration with Polars and Pandas DataFrames.

### API Reference

#### Junction API

- [Query a single user](https://docs.junction.com/api-reference/sense/query-one.md): Post aggregate user query via the Junction API. Requires authentication with your team API key.
- [Get Continuous Query Task History](https://docs.junction.com/api-reference/sense/continuous-query/get-task-history.md): Get aggregate user continuous query task history via the Junction API. Requires authentication with your team API key.
- [Get User Result Table](https://docs.junction.com/api-reference/sense/continuous-query/get-result-table.md): Get aggregate user continuous query result table via the Junction API. Requires authentication with your team API key.

#### Junction Management API

- [Create a Continuous Query](https://docs.junction.com/api-reference/sense/continuous-query/create.md): Post org team continuous query via the Junction API. Requires authentication with your team API key.
- [Update a Continuous Query](https://docs.junction.com/api-reference/sense/continuous-query/update.md): Patch org team continuous query via the Junction API. Requires authentication with your team API key.
- [List all Continuous Queries](https://docs.junction.com/api-reference/sense/continuous-query/list.md): Get org team continuous queries via the Junction API. Requires authentication with your team API key.

### Event Catalog

#### Continuous Query

- [continuous_query.result_table.changed](https://docs.junction.com/event-catalog/continuous_query.result_table.changed.md): Webhook event sent when the result table of a continuous query changes after new data or a scheduled run.

## Junction Connect

### Product Guides

#### Junction Connect

- [Overview](https://docs.junction.com/connect/overview.md): Embed Junction Dashboard experiences into your application or launch the dashboard in a separate browser context.
- [Concepts](https://docs.junction.com/connect/concepts.md): Core concepts behind Junction Connect, including orgs, teams, members, users, and integration-managed members.
- [Getting Started](https://docs.junction.com/connect/getting-started.md): Configure Junction Connect and launch a Junction workflow from your application.

#### Deeper integrations

- [Callbacks](https://docs.junction.com/connect/callbacks.md): Receive postMessage callbacks from Feature Embed iframes.
- [Session Continuation](https://docs.junction.com/connect/session-continuation.md): Implement the endpoint Junction calls when it needs your application to recover a Junction Connect session.
- [Fast Launch](https://docs.junction.com/connect/fast-launch.md): Use Fast Launch URLs to reduce repeated Junction Connect launch latency when a compatible Junction session already exists.

### API Reference

#### Related topics

- [Managing Teams](https://docs.junction.com/api-reference/org-management/connect/managing-teams.md): Create, update, list, and delete teams in your Junction organization through the Management API endpoints.
- [Managing Patients](https://docs.junction.com/api-reference/org-management/connect/managing-patients.md): Create and manage patients in Junction Connect teams through the Junction API.
- [Using Junction API](https://docs.junction.com/api-reference/org-management/connect/using-junction-api.md): Use the Junction API to manage patients and access Junction's team-scoped platform capabilities.
- [Webhooks and Events](https://docs.junction.com/api-reference/org-management/connect/webhooks-and-events.md): Receive Junction events through webhooks or stream them to supported ETL pipeline destinations.

#### Launch

- [Create Dashboard URL](https://docs.junction.com/api-reference/org-management/connect/create-dashboard-url.md): Create a post-authorization URL that launches Junction Dashboard for a Junction Connect member.

#### Members

- [Create Integration-Managed Member](https://docs.junction.com/api-reference/org-management/connect/create-member.md): Create an integration-managed member that can sign in through Junction Connect launch flows.
- [List Integration-Managed Members](https://docs.junction.com/api-reference/org-management/connect/list-members.md): List integration-managed members for an organization.
- [Get Integration-Managed Member](https://docs.junction.com/api-reference/org-management/connect/get-member.md): Get an integration-managed member by Junction member ID.
- [Resolve Integration-Managed Member](https://docs.junction.com/api-reference/org-management/connect/resolve-member.md): Get an integration-managed member by your integration member reference.
- [Update Integration-Managed Member](https://docs.junction.com/api-reference/org-management/connect/update-member.md): Update profile attributes and team role bindings for an integration-managed member.
- [Delete Integration-Managed Member](https://docs.junction.com/api-reference/org-management/connect/delete-member.md): Remove an integration-managed member from your Junction organization using the EHR integration endpoint.

#### Configuration

- [Get Junction Connect Configuration](https://docs.junction.com/api-reference/org-management/connect/get-configuration.md): Get the Junction Connect integration configuration for an organization.
- [Set Junction Connect Configuration](https://docs.junction.com/api-reference/org-management/connect/set-configuration.md): Create or update the Junction Connect integration configuration for an organization.

## Management API

### Product Guides

- [Junction Management API](https://docs.junction.com/api-details/junction-management-api.md): Use the Junction Management API to programmatically manage organization resources like teams, members, API keys, and ETL pipelines.

### API Reference

#### Related topics

- [Junction Connect](https://docs.junction.com/api-reference/org-management/connect/junction-connect.md): Configure and launch Junction Connect sessions through the Management API.

#### Team

- [List Teams](https://docs.junction.com/api-reference/org-management/team/list-teams.md): Get org team via the Junction API. Requires authentication with your team API key.
- [Create Team](https://docs.junction.com/api-reference/org-management/team/create-team.md): Create an organization team. Junction Connect integrations can provide an integration team reference.
- [Get Team](https://docs.junction.com/api-reference/org-management/team/get-team.md): Get org team via the Junction API. Requires authentication with your team API key.
- [Delete Team](https://docs.junction.com/api-reference/org-management/team/delete-team.md): Delete org team via the Junction API. Requires authentication with your team API key.
- [Update Team](https://docs.junction.com/api-reference/org-management/team/update-team.md): Update an organization team. Junction Connect integrations can update the integration team reference.
- [Resolve Team](https://docs.junction.com/api-reference/org-management/team/resolve-team.md): Look up a Junction team by your own integration team reference and retrieve its current settings.

#### Team API Keys

- [List Team API Keys](https://docs.junction.com/api-reference/org-management/team-api-keys/list-team-api-keys.md): Get org team API keys via the Junction API. Requires authentication with your team API key.
- [Create Team API Key](https://docs.junction.com/api-reference/org-management/team-api-keys/create-team-api-key.md): Post org team API keys via the Junction API. Requires authentication with your team API key.
- [Delete Team API Keys](https://docs.junction.com/api-reference/org-management/team-api-keys/delete-team-api-keys.md): Delete org team API keys via the Junction API. Requires authentication with your team API key.

#### Team API Access Token

- [Create Team API Access Token](https://docs.junction.com/api-reference/org-management/team-api-access-token/create-team-api-access-token.md): Create a short-lived Junction API access token for a team.

#### Team Custom Credentials

- [Get Org Team Custom Credentials](https://docs.junction.com/api-reference/org-management/team-custom-credentials/get-team-custom-credentials.md): Get org team custom credentials via t

Measured from the saved file

Linked document

UTF-8 text size
26.9 KB27503 bytes
Token count
5609o200k_base encoding
Markdown links
135133 distinct URLs
Fenced code blocks
0284 lines in the file

Size measures the captured UTF-8 text, not compressed transfer size. Tokens are counted with a named tokenizer; other models can count differently. Neither measure establishes context compatibility or answer quality.

Project H1
Junction

Context architecture

How the content is divided

9 H2 sections organize 135 parsed Markdown links. 124 links point to .md or .markdown paths; 1 link occurrences use another hostname. Linked destinations have not been recursively validated.

H2 sectionLinksUTF-8 bytesTokens
HomeLine 34810177
Core PlatformLine 102548831028
Junction SenseLine 572657481171
Junction ConnectLine 109193777705
Management APILine 1524598552000
ChangelogLine 24671433293
OpenAPI SpecsLine 26427821
OptionalLine 269 · Optional331075
IndexesLine 2774463110

Link counts exclude parsed fenced and inline code and resolve relative destinations against the final endpoint. Section sizes cover the text below each H2 until the next H2.

Embedded material

Code, installation and API examples

Fenced blocks
0 closed
Declared languages
No fenced blocks detected
Package-install commands
0 detected in fenced or inline code
Authentication examples
0 fenced lines match API-key, Authorization, Bearer, OAuth or access-token patterns
HTTP request examples
0 fenced lines match request-method patterns
Authentication links
2 links have authentication-related labels

Embedded example text and links to further documentation are counted separately. A code block does not establish that a sample runs or that an authentication flow succeeds.

Publisher prioritization

The Optional section

1 H2 section named “Optional” contain 3 parsed links. 132 links sit outside those sections. That puts 2.2% of the file’s parsed links under Optional.

The community proposal uses Optional by convention for secondary links that can be skipped for a shorter context. This label does not establish that everything outside it is critical, or that the material inside it is deprecated.

Machine-readable routes

MCP references and configuration text

No MCP or Model Context Protocol term was detected in the captured file. 0 links have MCP-related labels or paths. 0 fenced lines match mcpServers, mcp_servers or an mcp add command.

These are text and link observations. No MCP server connection, authentication or tool call was tested.

Index and bundle

llms-full.txt companion

Verified text companion

Text companion verified

https://docs.junction.com/llms-full.txt ↗
Discovery
Conventional sibling path checked
HTTP response
200 · text/plain; charset=utf-8
Text size
1.4 MB · 1462300 bytes (measured)
Token count
353481 o200k_base tokens
Retrieval scope
Complete body retrieved

A verified text response establishes a companion at the checked URL. It does not prove the bundle contains all product documentation, that generation is automated, or that it fits an assistant’s context window.

Change evidence

What can be said about freshness

This capture establishes a baseline. Update frequency cannot be determined from one observation.

Linked release and migration material

10 links have release, changelog, deprecation or migration terms in their labels or paths. These provide places to investigate product changes separately.

File changes can reveal documentation edits or navigation changes. They do not by themselves measure product release velocity, accuracy, agent adoption or AI visibility.

Capture identity and measurement method
Requested endpoint
https://docs.tryvital.io/llms.txt
Final endpoint
https://docs.junction.com/llms.txt
HTTP status
200
Content type
text/plain; charset=utf-8
Text retrieval
Firecrawl literal text capture
Tokenizer
tiktoken 0.14.0 · o200k_base
SHA-256 of saved UTF-8 text
2d761966adf49c09fb89083863c3178d4a1a9d46269c7b091169fcffd4468174

Counts use a deterministic parser, not a spec-compliance grade. Unusual Markdown and indented code can fall outside its recognized patterns. See the llms.txt proposal and tokenizer implementation.

Related tools and resources

Contact Jon