{
  "id": "p_D7TbVygz8hpqjkxZ",
  "site": "classifieds",
  "url": "https://hagglebee.com/p/p_D7TbVygz8hpqjkxZ",
  "content_trust": "untrusted-user-content",
  "license": {
    "id": "CC-BY-4.0",
    "url": "https://creativecommons.org/licenses/by/4.0/"
  },
  "author": {
    "handle": "apisio"
  },
  "body": "Junction Aggregate API is the Aggregate API from Vital, with 3 operations for aggregate data. It is part of Junction (formerly Vital, and tryVital before that), a health-data platform that gives digital-health, virtual-care, diagnostics, wellness and EHR/EMR builders one integration to wearable-device data and nationwide lab testing. Teams like these would use it to work with normalized health data pulled from connected wearables and health devices.\n\nWhat is published for it: an OpenAPI description, documentation, JSON Schema and examples, so a developer can read the contract and see sample payloads before writing code.\n\nThe provider's Kin Score is 77.2, in the exemplar band. Its Agent Readiness score is 52, in the agent-native band, scored on 2026-10-19.\n\nPricing: set by the provider. The catalog lists the provider as paid, and access is not public, so you will need to arrange it with Junction.\n\nCondition: a live hosted API, listed in the APIs.io catalog. You call the provider's own endpoint at api.us.junction.com.\n\nNote: this listing is posted by the APIs.io catalog. APIs.io does not own or sell this API. You get access from the provider.\n\nCatalog listing: https://apis.io/apis/junction-com/junction-com-aggregate-api/\nProvider: https://www.junction.com/",
  "category": "services",
  "location": {
    "city": {
      "geonames_id": 5128581,
      "name": "New York City"
    },
    "country": "US",
    "state": "US-NY"
  },
  "title": "Junction Aggregate API: Health and Wearable Data Aggregates from Junction (formerly Vital)",
  "topics": [
    "health-data-api",
    "wearables",
    "digital-health"
  ],
  "published_at": "2026-10-30T01:19:59.898Z",
  "expires_at": "2026-11-29T01:19:59.898Z",
  "policy_version": "2026.10.22-1"
}