OndaRx developer portal
OndaRx API and developer resources
The OndaRx API is a public, unauthenticated catalog so agents and integrators can discover treatments, marketing pages, and canonical URLs. This is not a clinical API: it does not collect patient history, process payments, or return PHI. Use the OndaRx OpenAPI specification when you need programmatic access to OndaRx product pages, then send people to the matching Get Started intake link from the catalog.
Authentication
Catalog endpoints require no API key. Intake (`/api/intake/*`), chatbot (`POST /api/chat`), cron, draft preview, and Payload CMS writes stay private. Do not send health information to the public API.
OndaRx API endpoints
- OndaRx OpenAPI specification at
/openapi.json GET /api/v1/health— livenessGET /api/v1/treatments— medication catalogGET /api/v1/treatments/{slug}— one medicationGET /api/v1/pages— indexable marketing URLs
Example request
curl -s https://ondarx.com/api/v1/treatments
OndaRx API rate limits
The default policy allows 120 requests per 60 seconds per client. Every OndaRx API response includes IETF RateLimit and RateLimit-Policy headers plus RateLimit-Limit and RateLimit-Reset so agents can self-throttle. RateLimit-Remaining is sent as 0 on HTTP 429 only. A 429 also sends Retry-After (delta-seconds).
OndaRx API errors
4xx and 5xx responses use RFC 9457 application/problem+json with type, title, status, detail, and a machine-readable code (treatment_not_found, rate_limited, internal_error). Unknown treatment slugs return 404.
OndaRx API internal error
HTTP 500 with code: internal_error means the public catalog could not complete the request. Retry later; do not send PHI to this API.
OndaRx MCP server
Follow llms.txt for when-to-use guidance. Content negotiation: send Accept: text/markdown to HTML routes for a markdown variant (Vary: Accept). The OndaRx MCP server uses Streamable HTTP at https://ondarx.com/mcp; the handshake lives at /.well-known/mcp. Sitemap: /sitemap.xml. Questions: help@ondarx.com.