Connect NoteScreen to your own tools.
NoteScreen doesn't have a self-serve developer API today. The check engine, the Scribe pipeline, and the EHR platform all run on internal service boundaries designed to keep PHI off any general hosting layer — none of that is opened up for outside integrations yet. Here's the shape of what's planned, and how to reach a human if you're building an integration now.
What is an API, in plain terms?
An API is a way for two pieces of software to talk to each other directly — no browser window, no copy-and-paste. It's how one tool can read from or write to another automatically.
NoteScreen doesn't offer one to outside developers yet. This page describes what it would look like if and when it does — nothing here is something you can call today.
For a developer.
The EHR platform's internal API is already built around a stable action contract (practices, clients, notes, appointments, BYO AI keys) — the same shape a public API would eventually expose.
Opening it up is a real roadmap item, gated on the platform moving past its current admin-only pilot.
Illustrative only — nothing below is live.
A sketch of the resources and endpoints a future API might expose. It is not available, not callable, and has no address to call. It's here so a developer can see where things are headed.
// Illustrative planned shape — NOT a live endpoint.
// No public API exists yet; nothing here is callable.
Note {
id // string
practice // which practice it belongs to
client // de-identified reference
appointment // the session it documents
format // "SOAP" | "DAP" | "BIRP"
status // "draft" — you approve before anything files
}Endpoint shapes
Planned — not live| Method | Resource | What it would do | Status |
|---|---|---|---|
| GET | /practices | List the practices you belong to | Planned |
| GET | /clients | List clients in a practice | Planned |
| POST | /notes | Create a note draft for review | Planned |
| GET | /notes/:id | Fetch a note you'd then approve | Planned |
| GET | /appointments | List appointments on the schedule | Planned |
These are illustrative resource shapes, not yet available. No endpoints are live, there is no base URL, and no keys are issued.
You probably don't need an API.
Already on an EHR we don't support?
If you're on an EHR NoteScreen doesn't already support out of the box, you don't need an API — the Scribe browser extension can be taught any web EHR's note field once, and it remembers.
Teaching Scribe an EHRSomething else?
For anything else — a partnership, an early look at API access, or a question a developer would ask — email us. That's the real way in today.
hello@notescreen.aiNo NoteScreen API is publicly available today. Everything shown above describes a planned shape, not a live service.