Short answer Partly
Moonshot EHR exposes a partner API for lead intake and public reads (service catalog and availability) behind owner-issued keys, an MCP server that lets an AI assistant query the clinic's own data under the clinic's permissions, and webhooks into the CRM from website forms. It is not a full clinical read-write API, and the partner API is currently offered to partners on request.
How it works in Moonshot
- Owners create API keys under Settings, Developers; keys are scoped to leads and public reads.
- The MCP endpoint is how Claude and other assistants read clinic data for the AI assistant feature, with the user's own permissions applied.
- Website form webhooks store lead state, request geo and quiz type into the CRM; website chat creates leads with its own source.
Limits, stated plainly
- No patient-record read or write API for third parties today.
- The partner API is a limited surface with a review date; build against it only after talking to Moonshot.
- No Zapier app.
Related
Questions people ask next
Can our marketing agency push leads into Moonshot?
Yes, through the partner API leads endpoints with a key the owner issues, or through form webhooks.
Can we pull our data out?
Chart packets, documents, CSV exports and the accounting journal are available to the clinic; patients can export their own data from the portal.
Is there an OpenAPI spec?
Yes, for the partner API surface, available with the key.
Checked against the product on October 18, 2026. If the product changes, this page changes with it; the changelog lists what shipped and when.