Professional by default
Clear navigation, accessible typography, and mobile-first layout. No clutter.
cbioapi.pharmacodb.ca is a landing page for a cBioPortal-compatible REST API. Use it to integrate analytics, build dashboards, or run reproducible pipelines. (cBioPortal provides a REST API and OpenAPI-based tooling for client generation.)
Tip: replace the placeholders below with your real base path and OpenAPI URL once available.
A concise entry point for developers and researchers: what the API is, how to use it, and where to find docs/spec. Keep it simple, fast to scan, and trustworthy.
Clear navigation, accessible typography, and mobile-first layout. No clutter.
Copy-paste cURL snippets and stable endpoints for scripts and pipelines.
Compatible approach inspired by cBioPortal REST conventions and tooling.
Link it here so users can generate clients (Python/R/JS) and explore the API via Swagger UI.
These examples are safe defaults for an API landing page. Replace BASE with your actual base path.
# Set your base URL
BASE="https://cbioapi.pharmacodb.ca"
# Health check (recommended endpoint)
curl -s "$BASE/health" | jq .
# List studies (example cBioPortal-style resource)
curl -s "$BASE/api/studies" | jq .
# Query a single study (example)
curl -s "$BASE/api/studies/{studyId}" | jq .
Note: If your deployment uses a different base path (e.g. /api/v1), update the snippets accordingly.
Keep endpoint lists short on the landing page—link to the full reference in OpenAPI/Docs.
GET /healthGET /versionGET /status
GET /api/studiesGET /api/studies/{id}
GET /api/samplesGET /api/mutationsGET /api/cna
# If you expose OpenAPI: # - Provide: /openapi.json (or /api-docs) # - Optional: Swagger UI at /docs # Users can generate clients (Python/R/JS) from the OpenAPI spec.
Short answers. No ambiguity.
This landing page describes a cBioPortal-compatible REST interface. For official cBioPortal API references and clients, consult the cBioPortal documentation.
If you publish one (recommended), link it from this page (e.g. /openapi.json or /api-docs) and optionally host Swagger UI at /docs.
Add a short policy section here: authentication method (none/API key/OAuth), rate limits, and contact for access.
Add a single, professional contact channel for API issues, access requests, and support.
Email: support@pharmacodb.ca (replace as needed)
Status: /status
Disclaimer: This page is informational and does not provide medical advice.