Lobbie API and EHR Integration Guide (2026)
CTO & Co-Founder
CTO & Co-Founder at Nirmitee.io. Architects healthcare integrations across FHIR, SMART on FHIR, ABDM and NHCX, writing from production experience taking hospital software from sandbox to go-live.

Lobbie is patient intake software. Patients fill in forms, consents and packets online before a visit, and the answers flow to the practice. Lobbie also sells its own EMR, which it says connects "intake, charting, labs, prescribing, scheduling, and billing in one place". So Lobbie can sit beside your EHR as an intake tool, or be the EMR itself.
For how this compares with other med spa and telehealth EHRs that GLP-1 programs use, see our GLP-1 clinic software prescribing integration guide.
The Lobbie Developer API is public at docs.lobbie.com. Lobbie says it can be used "to create, read, update and delete information about Locations, Patients and Forms within Lobbie". This guide is for a product lead or buyer who has to connect a product to Lobbie, and for the engineer who builds it. It covers access and every documented endpoint with its method and path. It shows a real request and response from the docs. It also covers the limits Lobbie states, the EHR interfaces Lobbie runs, and what Lobbie leaves unpublished. If you need a team to build it, see our EHR integration services. Last checked: Nov 18, 2026.
Lobbie API at a glance
| Question | Short answer |
|---|---|
| Who grants access? | You do, inside your own Lobbie account. A user with the Developer role creates the Client ID and Client Secret in Developer Settings. Lobbie's newer Partner API is provisioned by Lobbie. |
| Who signs? | Lobbie does not publish who on the customer side must sign, or whether it signs a BAA. |
| Are there public documents? | Yes. One reference page at docs.lobbie.com with curl examples. No Postman collection, OpenAPI file or SDK is linked from it. |
| Which routes exist? | The REST Developer API with webhooks, a Partner API in beta, and EHR interfaces that Lobbie's own team builds. |
| What does it cost? | Lobbie publishes no API fee and no EHR interface fee. |
| How long does it take? | Lobbie publishes no time for access, build or go-live. Keys are self-served, so the first sandbox call can happen as soon as a Developer user exists. |
| What is the biggest limit? | No appointment, billing or prescribing endpoints in the public API. |
What can you build with the Lobbie API?
Nine use cases follow. Each points to a row in the table of what you can read and write (section 6). Lobbie publishes no build times, so this guide gives no build estimate. Build complexity is our own rating.
1. Send intake packets when an appointment is booked in your system
- Who it is for: scheduling, practice management and telehealth products.
- The value: the patient gets the right forms before the visit without anyone at the front desk sending them.
- Build complexity: low to medium.
- How well it works: well. You create a form group (Lobbie also calls it a packet) with
POST /forms/groups, and the response holds the patient's link. The API has no appointment object. Your own system decides when to call. See rows R2 and R6.
2. Get completed answers back in real time
- Who it is for: EHRs, intake dashboards and care coordination tools.
- The value: answers land in your system the moment the patient finishes.
- Build complexity: low to medium.
- How well it works: well for the two events Lobbie supports: a patient completes a packet, and a staff member completes a packet. The body carries answers keyed by form element ID, plus a
mappedblock with names such asfirst_name. See row R10.
3. Prefill forms with data you already hold
- Who it is for: any system that already knows the patient.
- The value: returning patients do not type their details again.
- Build complexity: low.
- How well it works: well. At packet creation, you pass a map of key and value pairs in
prefill. Values you pass win over the other two prefill sources. See row R6.
4. File completed forms as a PDF in the chart
- Who it is for: EHRs and document management systems.
- The value: a signed, readable copy of every form sits in the record.
- Build complexity: low.
- How well it works: well. Create the PDF first, then retrieve it. Lobbie also says its Paperless product generates "PDFs suitable for upload into third-party EHRs". See row R8.
5. Load or sync a patient roster
- Who it is for: practices moving to Lobbie, and products that keep a roster in step.
- The value: patients exist in Lobbie before the first packet goes out.
- Build complexity: medium.
- How well it works: partly. Batch create takes up to 500 patients a call. There is no patient update endpoint in the public reference, so changes to existing patients need another route. See row R2.
6. Link family members
- Who it is for: pediatric, family and behavioral health practices.
- The value: a parent can be tied to a child's record.
- Build complexity: low.
- How well it works: well. Relationships such as parent and child are created in batches of up to 500. See row R2.
7. Set up staff and locations from your own admin system
- Who it is for: multi-site groups and MSOs that run their own user directory.
- The value: a new clinic or a new staff member is live in Lobbie without manual set-up.
- Build complexity: low.
- How well it works: well. Locations and staff each have create and update calls. Lobbie notes that deactivating a staff user stops their Developer API keys. See rows R1 and R7.
8. Delete patient data on request
- Who it is for: products with retention rules or erasure requests.
- The value: a documented way to remove a patient, a packet or a form.
- Build complexity: low, with care.
- How well it works: it works, and it cannot be undone. Lobbie writes that it "will NOT be able to recover data for you" after these calls. See row R9.
9. Watch for failed webhooks and replay them
- Who it is for: any team that runs the webhook receiver in production.
- The value: you find a missed delivery and send it again.
- Build complexity: low.
- How well it works: well.
GET /webhook-requests?success=falselists failed attempts, and a replay call resends one. See row R10.
The nine Lobbie use cases compared
| Use case | Who it is for | Build complexity (our rating) | Row in the read and write table |
|---|---|---|---|
| 1. Send packets when an appointment is booked | Scheduling and PM products | Low to medium | R2, R6 |
| 2. Completed answers in real time | EHRs and intake tools | Low to medium | R10 |
| 3. Prefill forms | Any system that knows the patient | Low | R6 |
| 4. File forms as PDF in the chart | EHRs and document systems | Low | R8 |
| 5. Load or sync a patient roster | Migrations and roster sync | Medium | R2 |
| 6. Link family members | Pediatric and family practices | Low | R2 |
| 7. Staff and locations from your admin | Multi-site groups and MSOs | Low | R1, R7 |
| 8. Delete patient data on request | Retention and erasure flows | Low | R9 |
| 9. Watch and replay failed webhooks | Teams running the receiver | Low | R10 |
How do you get access to the Lobbie API?
You need a Lobbie customer account. A user with the Developer role logs in and creates a Client ID and Client Secret on the Developer Settings page. Developer is a staff role in Lobbie's role list. No public developer sign-up page is published.
The steps for the Developer API
- The practice, or the product company that holds the Lobbie account, gives a staff user the Developer role.
- That user opens Developer Settings and creates the Client ID and Client Secret.
- Your server exchanges them for an access token at the sandbox auth host first, then at production.
If you are a vendor without a Lobbie account
Lobbie does not publish how a third-party vendor gets a sandbox without being a customer. Its release notes describe a second API, the Partner API, whose integrators are set up by Lobbie's own superadmins. Lobbie noted on Jun 25, 2026 that it was "still in BETA and being tested by a select number of accounts". Ask Lobbie whether you can join it.
How practices turn on an EHR interface
Lobbie's own team builds and manages the EHR interfaces. Lobbie says its athenahealth integration is "managed by a team skilled in HL7v2, FHIR, proprietary APIs, data extracts and more". For DrChrono, the help center says Lobbie "typically configures" it during onboarding. After that the practice keeps it current in its own account. For the EHR side of these connections, see our athenahealth API guide and our DrChrono API guide.
| EHR | Who sets it up | What the practice does afterwards |
|---|---|---|
| athenahealth | Lobbie's integration team | Lobbie publishes no customer steps |
| AdvancedMD | Lobbie's integration team | Lobbie publishes no customer steps |
| DrChrono | Lobbie, during onboarding | Enable practitioners and appointment types under Settings > Integrations EHR > DrChrono, then attach form templates to each appointment type |
Who on the customer side must sign for API access or an EHR interface is not published.
What does Lobbie API access give you?
Two environments, each with its own auth host and API host, and read and write access to the intake data in the account.
Environments
| Environment | Auth host | API host |
|---|---|---|
| Sandbox | auth-sandbox.lobbie.com | api-sandbox.lobbie.com |
| Production | auth.lobbie.com | api.lobbie.com |
Every path sits under /lobbie/api/developer/v1. Lobbie's examples all point at the sandbox "to make sure that if you copy + paste an example your production environment is not affected". Lobbie does not say whether sandbox data and features match production.
The data that opens up
Locations, patients, patient tags, form templates and template groups, form attributes and elements, form groups or packets with their forms and answers, staff, PDFs and the webhook log.
What are the ways to integrate with Lobbie?
Four routes are published. Two you build yourself, and two Lobbie runs.
| Route | What it is | When it fits |
|---|---|---|
| Developer API | REST and JSON, OAuth2 client credentials, sandbox and production hosts | You hold or serve a Lobbie account and want to create packets, read answers and manage patients |
| Webhooks | At packet completion, Lobbie calls your endpoint. You pick the method (GET, POST, PUT or PATCH) and how Lobbie authenticates (OAuth2 or API key) | You want answers pushed, not polled |
| Partner API (beta) | A second API, version 2, provisioned by Lobbie, with its reference on Redocly | Lobbie lets you into the beta |
| Lobbie-built EHR interfaces | Two-way interfaces to athenahealth, AdvancedMD and DrChrono, run by Lobbie's team using HL7 v2, FHIR, vendor APIs, data extracts and SFTP | The practice runs one of those EHRs and wants intake to flow into it |
Lobbie calls its interface layer the Integration Manager. It also runs a Labcorp connection for lab orders and results inside Lobbie, and Labcorp results arrive by HL7.
What the Partner API release notes list
The Partner API reference is not linked from docs.lobbie.com, so what follows comes from Lobbie's own release notes. They list appointment create and update ("POST and PUT appointment endpoints"), patient endpoints, read-only payments, payment attempts and invoices, and lab endpoints "deployed for testing". They also list webhooks for patient and appointment events, webhook management calls, and an OpenAPI specification for the webhook envelope. Check what your account can call before you design around it.
What can you read and write with the Lobbie API?
The public reference lists 44 method and path pairs, counting aliases such as /print and /pdf separately. All paths below sit under https://api-sandbox.lobbie.com/lobbie/api/developer/v1 for the sandbox.
| Row | Resource | Methods and paths | Read or write |
|---|---|---|---|
| R1 | Locations | GET /locations, GET /locations/{id}, POST /locations/create, POST /locations/update | Read and write |
| R2 | Patients | GET /patients, GET /patients/{id}, GET /patients/search, POST /patients/batch (up to 500), POST /patients/relationships (up to 500) | Read and create. No update |
| R3 | Patient tags | GET /patient-tags | Read |
| R4 | Form templates | GET /forms/templates, GET /forms/templates/{id} | Read |
| R5 | Form template groups | GET, POST and PUT /forms/templates/groups, GET /forms/templates/groups/{id}, GET /forms/templates/groups/practitioner/{id} | Read and write |
| R6 | Form groups or packets | GET, POST and PUT /forms/groups (alias /forms/packets), GET /forms/groups/{id} with answers, mapped answers and PDF, PUT /forms/groups/archive | Read and write |
| R7 | Staff | GET /staff, GET /staff/{id}, POST /staff, PUT /staff | Read and write |
| R8 | POST /forms/pdf/create (alias /forms/print/create), POST /forms/pdf/retrieve | Create and read | |
| R9 | Destroy | DELETE /destroy/patient, DELETE /destroy/form/group (alias /packet), DELETE /destroy/form | Delete, not recoverable |
| R10 | Webhooks | Two events: patient completes a packet, staff completes a packet. GET /webhook-requests, POST /webhook-requests/{id}/replay | Push to you, plus log and replay |
| R11 | Form attributes and elements | GET /forms/templates/attributes, GET /forms/templates/attributes/names, GET /forms/templates/elements, PUT /forms/templates/elements/update, PUT /forms/templates/elements/update/{id} | Read, and update elements |
| R12 | Single form | GET /forms/{id} | Read |
What Lobbie's own EHR interfaces move
Lobbie's athenahealth, AdvancedMD and DrChrono pages use the same wording.
| Row | Direction | What moves |
|---|---|---|
| E1 | Lobbie to EHR | New patients who fill in forms in Lobbie are created in the EHR |
| E2 | Lobbie to EHR | Forms go to the patient's chart as PDF documents |
| E3 | Lobbie to EHR | Demographics update, automatically or by hand, from form answers |
| E4 | Lobbie to EHR | Appointments update, automatically or by hand, from form answers |
| E5 | EHR to Lobbie | A new appointment in the EHR sends the matching Lobbie forms to the patient |
| E6 | Lobbie to EHR | Insurance details and consent forms update |
For DrChrono, the help center adds that completed forms go back "attached to the appointment record".
What is not possible with the Lobbie API?
The public reference covers intake. It leaves out most of what Lobbie's EMR does.
| Not in the public Developer API | The usual workaround |
|---|---|
| Appointments and scheduling. The appointment ID shows up only as a webhook query value. | Trigger packets from your own scheduler. Ask about the Partner API beta, whose release notes list appointment create and update. |
| Patient update. Patients can be created, searched, read and deleted, not changed. | Pass current values as prefill on each packet, or ask Lobbie about the Partner API patient endpoints. |
| Billing, payments, messaging, reminders and NPS. | The Partner API release notes list read-only payments and invoices. Messaging has no API route in either source. |
| EMR charting, labs and prescribing. | Lobbie's EMR includes prescribing, but neither the public reference nor the Partner API release notes list a prescribing endpoint. Lab endpoints appear only as "deployed for testing". |
| Creating a form template. Templates can be read and their elements updated. | Build templates in Lobbie's own screens, then read their IDs. If your own product needs forms in a standard shape, see our FHIR Questionnaire guide. |
| Webhooks for packet created, viewed or expired. Only the two completion events exist. | Poll GET /forms/groups for status. |
| FHIR or HL7 endpoints. The only FHIR mention is a value set reference for gender. | Lobbie's own team runs HL7 and FHIR for its EHR interfaces. |
| A full list of EHRs. The site says "most common EHRs" but names three. | Ask Lobbie for the list and the route for your EHR. |
So the plain answer on prescribing: Lobbie's EMR prescribes, and its API does not.
What are the Lobbie API limits?
Lobbie publishes page sizes and batch caps. It does not publish rate limit numbers or the token lifetime.
| Limit | Value | Source |
|---|---|---|
| Batch patient create | 500 a call | |
| Patient relationships | 500 a call | |
| Form group list | Default 10 a page, with a page offset | |
| Webhook log | Default 10, maximum 100 a page | |
| Patient list | No paging parameters documented | |
| Signed file links | Expire after 86,399 seconds, about 24 hours, in the examples | |
| Packet due date | Patients cannot open a packet after its due date, and due dates snap to 11:59:59 PM location time | |
| Rate limits | They exist on the API Gateway for the Partner API, and token requests are throttled to push token caching. Numbers not published |
How much does Lobbie integration cost?
Lobbie publishes no fee for API access, per call or for an EHR interface, and the lobbie.com sitemap has no pricing page. Ask Lobbie:
- Is Developer API access included in our plan, or priced on its own?
- Is there a fee for the athenahealth, AdvancedMD or DrChrono interface, at set-up or each month?
- Does the Partner API carry a fee?
How long does a Lobbie integration take?
Lobbie publishes no time for access, build, testing or go-live, and no time to set up an EHR interface. One part is fast by design: keys are self-served in Developer Settings, so the wait is only for a user with the Developer role. Ask Lobbie how long an EHR interface takes from signed order to live, and who on its team owns it.
How do you build a Lobbie API integration, step by step?
Six steps cover the usual intake flow: token, IDs, patient, packet, answers, PDF.
Step 1. Get an access token
Lobbie uses the OAuth2 client credentials flow. This is the example in Lobbie's docs, with the keys left as placeholders:
curl -X POST \
https://auth-sandbox.lobbie.com/oauth2/token \
-H "authorization: Basic \"$(echo -n '<client_id>:<client_secret>' | base64)\"" \
-H 'content-type: application/x-www-form-urlencoded' \
-d 'grant_type=client_credentials'
Send the token on every call as Authorization: Bearer <token>. Cache it. Lobbie throttles the token endpoint on its gateway.
Step 2. Read the IDs you need
Call GET /locations and GET /forms/templates/groups to get the locationId and formTemplateGroupId for the packet.
Step 3. Find or create the patient
Search with GET /patients/search by name, email, mobile phone or date of birth in MM/DD/YYYY. At packet creation, a patient with an id tells Lobbie to use that patient. Without one, "Lobbie will try to create a new Patient before proceeding".
Step 4. Create the packet
This is the request and response in Lobbie's docs:
curl -X POST \
https://api-sandbox.lobbie.com/lobbie/api/developer/v1/forms/groups \
-H "Authorization: Bearer $LOBBIE_ACCESS_TOKEN" \
--data "{
formTemplateGroupId: 1,
locationId: 1,
dueDateUnix: 1690811324454,
patient: {
firstName: \"Neato\",
lastName: \"Burrito\",
email: \"burrito@lobbie.com\",
dateOfBirth: \"01/01/2000\"
},
prefill: {
first_name: \"Taco\",
last_name: \"Nacho\"
}
}"
{
"success": true,
"message": "Forms created.",
"data": {
"id": 52,
"locationId": 1,
"patientId": 1,
"dueDateUnix": 1690873199000,
"urls": {
"patient": "https://localhost:3000/forms/patient?token=oso9NmuIqa2lqhTVNaaaBkadErMrzsXG",
"staff": "https://localhost:3000/home/patients/fb924039-ed0f-4214-9196-a7fc33cd3619/1"
}
}
}
urls.patient is the link the patient opens. Note the due date in the response: Lobbie moved it to the end of the day. Sending the same request twice creates two packets.
Step 5. Receive the answers
Set up webhooks once for the account. "The settings for your webhooks are maintained on an Account level." With a GET webhook, Lobbie sends formGroupId, patientId and, when there is one, appointmentId as query values. With any other method it sends the packet in the body, with answers keyed by form element ID, a mapped block and a signedURL.
Step 6. File the PDF and watch for failures
Create the PDF with POST /forms/pdf/create, then fetch it with POST /forms/pdf/retrieve, and write it to the chart. Each day, list failed deliveries with GET /webhook-requests?success=false and replay them.
Which Lobbie API quirks should you know?
Each one comes from Lobbie's docs or release notes.
Errors come back as HTTP 200
Lobbie says every response "should result in a 200". Check success in the body, and read message when it is false.
Creating a packet is not idempotent
"Sending the same request again will result in a duplicate Form Group/Packet being created." Store the returned id and check before you retry.
Updating a template group replaces its list
"You MUST pass the existing formTemplateIds" or the ones you leave out are removed.
Setting status 0 fires a webhook
Forcing a packet to complete triggers the staff-complete webhook, so your receiver sees an event you caused.
Three date formats
Search takes date of birth as MM/DD/YYYY, batch create takes YYYY-MM-DD, and timestamps are epoch milliseconds. The sample search response returns "8/10/2003", with no leading zero.
Staff-only answers differ by webhook
The patient webhook leaves out answers to staff-only form elements. The staff webhook includes them.
Answers are keyed by element ID
Use the mapped block for names such as first_name and date_of_birth, or map element IDs yourself.
Template versions move
When Lobbie updates a form template, its version goes up by 1, and new forms use the latest version.
Prefill has an order
Values you pass come first, then patient lifecycle attributes, then the patient record.
The docs have small slips
"Delete a Form Template Group" is documented as a PUT, and some location examples leave "Bearer" out of the header.
Timeouts show as 504
A webhook that times out is logged with status 504 "Connection timeout". The automatic retry policy is not stated. For the Partner API, Lobbie says endpoints that fail again and again are turned off and the partner is told.
What should you check before you sign with Lobbie?
Check security terms, destroy calls and webhook auth, then ask Lobbie the open questions below.
Security, as Lobbie states it
Lobbie states it is "Fully HIPAA-compliant" and that "All assets are encrypted by default". This is Lobbie's own statement, not a certification. Lobbie publishes nothing on a BAA, SOC 2, HITRUST or data residency. Its examples show AWS us-east-2. The release notes say the API gateway enforces TLS 1.2 at minimum and runs a web application firewall.
Rules for your side
- Keep the Client Secret on your server. Deactivating the staff user stops their keys, so tie each key to a named Developer user.
- Protect your webhook endpoint. Lobbie authenticates with OAuth2 or an API key that you set, and documents no payload signature.
- Signed PDF links expire in about 24 hours in the examples, so fetch and store the file.
- Gate every destroy call behind a human check. Lobbie cannot recover the data.
Testing
Build against the sandbox hosts, as Lobbie's examples do. Test duplicates, a packet past its due date, a staff-forced completion and a webhook timeout.
Questions to ask Lobbie before you sign
- Do you sign a BAA with us, and who signs on our side?
- How does a vendor without a Lobbie account get a sandbox?
- Can we join the Partner API beta, and which endpoints would we get?
- What are the rate limits and the token lifetime?
- Is there a fee for API access or for an EHR interface?
- How long does an athenahealth, AdvancedMD or DrChrono interface take to go live?
- Which other EHRs do you connect to, and by which route?
- Which HL7 message types or FHIR resources does each interface use?
- What is the webhook retry policy on the Developer API?
- Does the sandbox hold the same features as production?
- What support channel and response time do API developers get?
What is the next step for a Lobbie integration?
Planning a Lobbie integration? We scope the endpoints, the webhooks and the EHR route with you. Start at our EHR integration service.
Ready to scale?
Talk to our healthcare engineering team about building, integrating, and shipping faster.
Frequently Asked Questions
Does Lobbie have an API?
Is there a Lobbie API sandbox?
How do I get Lobbie API keys?
Which EHRs does Lobbie integrate with?
Does Lobbie support FHIR or HL7?
Can I get Lobbie form answers in real time?
Can I create appointments through the Lobbie API?
Does the Lobbie API support prescribing?
What does the Lobbie API cost?
Is Lobbie HIPAA compliant?


