Carium Lachesis API

openapi: 3.2.0
info:
  title: Carium Lachesis API
  version: '2026-10-07'
  description: 'GENERATED FROM DOCUMENTATION by API Evangelist on 2026-10-07: 26 operation(s) read from 5 public documentation page(s) (each operation names its page in x-source). This is not the provider''s published contract; Carium has published no machine-readable contract that the pipeline could find. Engine: local.'
  x-evidence-tiers:
    code-example: 8
    documentation: 18
    pages-with-code: 3
    pages-read: 5
  x-generated-from: documentation
  x-provenance: generated
  x-authored-by: API Evangelist
  x-generated: '2026-10-07'
  x-generator: generate-contract-from-docs.py
  x-engine: local
  x-sources:
  - https://developers.carium.com/docs/main/api/intro
  - https://developers.carium.com/docs/main/api/examples
  - https://developers.carium.com/docs/main/areas/metrics
  - https://developers.carium.com/docs/main/guides/pathways_intro/part_1
  - https://developers.carium.com/docs/main/guides/pathways_intro/part_2
servers:
- url: https://api.carium.com
security:
- bearer: []
tags:
- name: Lachesis
paths:
  /lachesis/v1/timeseries:
    get:
      operationId: get_lachesis_v1_timeseries
      tags:
      - Lachesis
      summary: Querying metrics is done through the GET /lachesis/v1/timeseries/ API
      description: Querying metrics returns a paged response across the entire time range of the metric, optionally narrowed by begin-datetime and end-datetime.
      x-source: https://developers.carium.com/docs/main/areas/metrics
      parameters:
      - name: individual-id
        in: query
        required: true
        schema:
          type: string
        description: The individual ID
      - name: type
        in: query
        required: true
        schema:
          type: string
        description: Metric type to query
      - name: begin-datetime
        in: query
        required: false
        schema:
          type: string
        description: Start of the time range
      - name: end-datetime
        in: query
        required: false
        schema:
          type: string
        description: End of the time range
      responses:
        '200':
          description: Success (status as documented)
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/GetLachesisV1TimeseriesResponse'
      x-evidence:
        kind: documentation
    post:
      operationId: post_lachesis_v1_timeseries
      tags:
      - Lachesis
      summary: Uploading various metrics for a single individual
      description: You can push metrics to the Carium API using the POST /lachesis/v1/timeseries/ API. You should send no more than 128kb of data per request.
      x-source: https://developers.carium.com/docs/main/areas/metrics
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/PostLachesisV1TimeseriesRequest'
      responses:
        '201':
          description: Success (status as documented)
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/PostLachesisV1TimeseriesResponse'
      x-evidence:
        kind: documentation
components:
  schemas:
    PostLachesisV1TimeseriesResponse:
      type: object
      properties:
        data:
          type: array
          description: Array of created timeseries objects
    GetLachesisV1TimeseriesResponse:
      type: object
      properties:
        data:
          type: array
          description: Array of metric data points
        data[].time:
          type: string
          description: Timestamp of the metric point
        data[].systolic:
          type: integer
          description: Systolic value (if present)
        data[].diastolic:
          type: integer
          description: Diastolic value (if present)
        data[].tags:
          type: string
          description: Optional tags
    PostLachesisV1TimeseriesRequest:
      type: object
      properties:
        data:
          type: array
          description: Array of timeseries objects
        data[].type:
          type: string
          description: Should be "time-series"
        data[].attributes.individual-id:
          type: string
          description: The individual ID
        data[].attributes.type:
          type: string
          description: Metric type (e.g., BodyMass)
        data[].attributes.data:
          type: array
          description: Array of metric data points
        data[].attributes.data[].type:
          type: string
          description: Metric point type (e.g., BloodGlucose, BloodPressure, BodyMass, OxygenSaturation, Pulse)
        data[].attributes.data[].time:
          type: string
          description: Timestamp of the metric point
        data[].attributes.data[].value:
          type: number
          description: Value for simple metric points
        data[].attributes.data[].context:
          type: string
          description: Context for metrics that require it (e.g., FASTING)
        data[].attributes.data[].systolic:
          type: integer
          description: Systolic value for BloodPressure
        data[].attributes.data[].diastolic:
          type: integer
          description: Diastolic value for BloodPressure
      required:
      - data
      - data[].type
      - data[].attributes.individual-id
      - data[].attributes.type
      - data[].attributes.data
      - data[].attributes.data[].type
      - data[].attributes.data[].time
  securitySchemes:
    bearer:
      type: http
      scheme: bearer