Carium Overlord API

The Overlord API from Carium — 2 operation(s) for overlord.

Operations 2

GET /overlord/v1/pathway-specs GET /overlord/v1/pathway-specs #
GET /overlord/v1/pathway-specs/ Pathway specs GET Request #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/carium:carium-overlord-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

carium-overlord-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Carium Overlord 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: Overlord
paths:
  /overlord/v1/pathway-specs:
    get:
      operationId: get_overlord_v1_pathway_specs
      tags:
      - Overlord
      summary: GET /overlord/v1/pathway-specs
      x-source: https://developers.carium.com/docs/main/guides/pathways_intro/part_2
      parameters:
      - name: organization-id
        in: query
        required: false
        schema:
          type: string
      - name: page[limit]
        in: query
        required: false
        schema:
          type: string
      - name: page[offset]
        in: query
        required: false
        schema:
          type: string
      responses:
        '200':
          description: Success (shape read from the example response on the page)
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/GetOverlordV1PathwaySpecsResponse'
      x-evidence:
        kind: code-example
        language: curl
        snippet: "curl ​ \n Pathway specs GET Request curl -X 'GET' \\ 'https://api.carium.com/overlord/v1/pathway-specs/?organization-id=f68573e8-b79f-42dc-9292-2d7ba43c9f33&page%5Blimit%5D=100&page%5Boffset%5D=0' \\ -H 'accept: application/vnd.api+json' \\ -H 'authorization: Bearer XXX' \n Enroll ​ \n Adding a patient to a pathway \n Enter patient ID: 1aa89840-8024-11eb-8cb7-8272b343556c Choose an option: 1 . Show pathw"
  /overlord/v1/pathway-specs/:
    get:
      operationId: getOverlordV1PathwaySpecs
      tags:
      - Overlord
      summary: Pathway specs GET Request
      description: Retrieves pathway specifications for an organization.
      x-source: https://developers.carium.com/docs/main/guides/pathways_intro/part_2
      parameters:
      - name: organization-id
        in: query
        required: true
        schema:
          type: string
      - name: page[limit]
        in: query
        required: false
        schema:
          type: integer
      - name: page[offset]
        in: query
        required: false
        schema:
          type: integer
      responses:
        '200':
          description: Success (status as documented)
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/GetOverlordV1PathwaySpecsResponse2'
      x-evidence:
        kind: documentation
      x-operation-id-source: normalized
      x-operation-id-original: get_overlord_v1_pathway_specs
components:
  schemas:
    GetOverlordV1PathwaySpecsResponse:
      type: object
      properties:
        page[offset]:
          type: integer
        page[limit]:
          type: integer
        page[total]:
          type: integer
    GetOverlordV1PathwaySpecsResponse2:
      type: object
      properties:
        meta:
          type: object
          description: paging information
        data:
          type: array
          description: list of pathway specs
        data.type:
          type: string
        data.id:
          type: string
        data.attributes:
          type: object
        data.attributes.name:
          type: string
        data.attributes.version.id:
          type: string
        data.attributes.version.name:
          type: string
  securitySchemes:
    bearer:
      type: http
      scheme: bearer