Public Mode
For integration reads and production consumption.
Managed-key product: kg.public. Human roles: consumer, clinician, service, partner, admin.
This page is the practical starter for Mountain Path KG integrations. Get auth, run a real request, and validate response shape before moving to Swagger.
Choose auth: X-API-Key or Bearer JWT.
Call /v1/graph/public/status to verify access.
Run your target read endpoint using public mode.
/v1/graph/{mode}/....public for partner-facing reads.draft only for internal author/admin workflows.Use this before diving into full schema docs.
X-API-Key: <key>Authorization: ApiKey <key>Authorization: Bearer <jwt>curl -H "X-API-Key: <KEY>" "http://mpkgapi.mountainlabs.online/v1/graph/public/status"
{
"mode": "public",
"ok": true
}
Human sessions use roles. Managed API keys require a matching environment, product, and endpoint scope.
For integration reads and production consumption.
Managed-key product: kg.public. Human roles: consumer, clinician, service, partner, admin.
For internal authoring and pre-publication workflows only.
Managed-key product: kg.draft. Human roles: reviewer, author, admin. Requires an isolated draft projection.
Either key-based or JWT auth is accepted.
X-API-Key: <key>
Authorization: ApiKey <key>
Authorization: Bearer <jwt>
Use this grouping to avoid guessing where each call belongs.
Use these before business calls.
Liveness check for monitoring.
Confirms auth + graph responsiveness.
Lists labels, relationships, properties.
Primary clinical retrieval endpoints.
Optional depth 1-4. Returns protocol-centered subgraph.
Supports limit, offset for pagination.
Query params: entity, query, limit.
Advanced integration and lineage scenarios.
Use start_label, start_id, max_depth, optional relationship_types.
Body shape: {"params":{...}}. Executes saved template query.
Replace only IDs and credentials. Keep URLs and structure unchanged.
curl -H "X-API-Key: <KEY>" "http://mpkgapi.mountainlabs.online/v1/graph/public/protocols/TYPHOID_V1.0?depth=3"
curl -H "X-API-Key: <KEY>" "http://mpkgapi.mountainlabs.online/v1/graph/public/drugs/CEFTRIAXONE?limit=50&offset=0"
curl -H "X-API-Key: <KEY>" "http://mpkgapi.mountainlabs.online/v1/graph/public/search?entity=protocol&query=typhoid&limit=10"
curl -H "X-API-Key: <KEY>" "http://mpkgapi.mountainlabs.online/v1/graph/public/paths?start_label=IllnessProtocol&start_id=TYPHOID_V1.0&max_depth=3"
curl -X POST -H "X-API-Key: <KEY>" -H "Content-Type: application/json" -d '{"params": {"protocol_id": "TYPHOID_V1.0"}}' "http://mpkgapi.mountainlabs.online/v1/graph/public/query/citation_lineage"
Every endpoint returns a stable wrapper around data payloads.
{
"mode": "public",
"nodes": [...],
"relationships": [...],
"metadata": { "protocolId": "TYPHOID_V1.0", "mode": "public" }
}
Integration note
Most integration failures map to these status codes.
Missing or invalid credentials.
Insufficient role for requested graph mode.
Entity not found in the graph.
Upstream Neo4j connectivity error.