PatientPop API
PatientPop, now part of Tebra, is a practice growth platform that helps independent healthcare practices acquire and retain patients through SEO, custom websites, online scheduling, reputation management, and patient communication. An unofficial API lets you programmatically pull patients, appointments, reviews, provider profiles, and directory listings—and push updates like new bookings, review responses, and profile changes back into PatientPop.
What is PatientPop?
PatientPop, now part of Tebra, is a practice growth platform that helps independent healthcare practices attract, book, and retain patients. Practices use PatientPop to run search engine optimization and paid advertising, publish a conversion-focused practice website, let patients book appointments online, manage their online reputation and reviews, communicate with patients via text, and track performance through reporting and analytics—all from a single dashboard.
Core product areas include:
- Patient Acquisition (SEO, Google Ads, and social media marketing on Facebook and Instagram)
- Practice Website (custom, conversion-focused sites with content management and blog publishing)
- Online Scheduling (direct booking through the website, online listings, and search engines)
- Reputation Management (review collection, response management, and real-time monitoring)
- Patient Communication (text messaging, appointment reminders, and patient engagement)
- Analytics & Reporting (campaign performance, conversion tracking, and ROI measurement)
Common data entities:
- Patients, Contacts, Leads, Patient Profiles
- Appointments, Bookings, Availability, Reminders
- Reviews, Ratings, Review Responses, Reputation Scores
- Providers, Practices, Locations, Directory Listings
- Campaigns, Web Traffic, Conversions, Analytics Reports
- Messages, Text Threads, Communication Logs
The PatientPop Integration Challenge
Practices run patient acquisition and front-office workflows on PatientPop every day, but turning a portal-driven growth platform into API-driven automation is non-trivial:
- No public developer API: PatientPop exposes its data through its web dashboard, not a documented partner API, so there is no standard endpoint to integrate against
- Tebra platform consolidation: PatientPop is now part of Tebra, and data spans practice growth, scheduling, and reputation surfaces with their own object models and IDs
- Authentication and session gates: Dashboard access is account- and role-scoped, and headless automation must handle login, session refresh, and any MFA
- Review and listing data spread: Reputation data is aggregated from multiple directories and review sites, making consistent extraction across sources difficult
- Scheduling data tied to the website: Online bookings flow through PatientPop's hosted scheduling widget rather than an open calendar API
- HIPAA-sensitive patient data: Patient contact details and appointment records require careful, compliant handling on every read and write
How Supergood Creates PatientPop APIs
Supergood reverse-engineers PatientPop's authenticated dashboard flows to deliver a resilient API layer for your practice account—covering patient, appointment, review, and listing data without waiting on a public API.
- Handles username/password login and MFA (SMS, email, TOTP) securely
- Maintains session continuity with automated refresh and change detection
- Normalizes responses across patients, appointments, reviews, and directory listings so you integrate once and rely on consistent objects
- Aligns with your practice account's roles, locations, and entitlements to ensure compliant access
Use PatientPop with AI agents: PatientPop MCP Server →
Getting Started
- Schedule Integration Assessment
Book a 30-minute session to confirm your practice account, locations, and authentication model.
- Supergood Generates and Validates Your API
We deliver a production-ready PatientPop adapter tailored to your account configuration and entitlements.
- Deploy with Monitoring
Go live with continuous monitoring and automatic adjustments as PatientPop and Tebra evolve.
API Endpoints
Authentication
/authenticateAuthenticate to a PatientPop practice account using username/password, or MFA, and obtain a session token for downstream calls.
Patient Operations
/patientsList patients and contact records with filters for location, status, acquisition source, and date range.
Scheduling
/appointmentsRetrieve appointments and online bookings with provider, location, and status filters.
Scheduling
/create_appointmentCreate or book a new appointment against a provider's availability for a given location.
Reputation
/reviewsPull aggregated reviews, ratings, and reputation scores across connected directories and review sites.
Reputation
/respond_reviewPost a response to a patient review and sync it back to the originating directory.
Use Cases
Sync patient and appointment data into your systems
- Pull new patients, leads, and contact records into a CRM or data warehouse - Stream online bookings and appointment changes to downstream scheduling and EHR tools - Reconcile acquisition source and conversion data for unified patient 360
Automate reputation and review workflows
- Pull aggregated reviews and ratings across directories into a single dashboard - Trigger automated or templated responses to new patient reviews - Route negative feedback to staff for fast service recovery
Track acquisition and marketing performance
- Sync campaign, web traffic, and conversion metrics into BI and reporting tools - Attribute new patient bookings back to SEO, ads, and listing sources - Surface ROI and cost-per-acquisition across locations
Keep provider and listing data in sync
- Pull provider profiles, practices, and locations for downstream directories - Push profile and listing updates to keep online presence consistent - Monitor directory listing accuracy across review and search platforms
Technical Specifications
Authentication
Username/password and MFA (SMS, email, TOTP) handled in a managed session
Connectivity
Authenticated dashboard flows reverse-engineered from PatientPop's web application
Response format
Normalized JSON across patients, appointments, reviews, providers, and listings
Rate limits
Adaptive throttling tuned to your practice account to avoid platform-side limits
Session management
Automatic session refresh, MFA replay handling, and credential rotation
Data freshness
Near real-time pulls for patients, appointments, and reviews with optional scheduled batch syncs
Security
Encrypted credential vault, scoped access tokens, HIPAA-aligned and SOC 2-aligned controls, and audit logging
Webhooks
Event-style callbacks for new patients, bookings, review activity, and listing changes
Latency
Sub-second reads on cached entities; multi-second writes when posting bookings and review responses
Throughput
Horizontally scaled workers sized to multi-location practice volume
Reliability
Retry, backoff, and idempotency keys for booking and review-response operations
Adaptation
Continuous monitoring of PatientPop and Tebra platform changes and account configuration drift
Frequently asked questions
PatientPop does not publish a documented developer API; its data is exposed through its web dashboard. Supergood provides an API layer by reverse-engineering the authenticated dashboard flows, so you can integrate without waiting on a public API.
PatientPop is now part of Tebra, and Supergood works against your existing PatientPop practice account and authenticated sessions. We adapt to platform consolidation so your integration keeps working as surfaces move under Tebra.
Yes. Reviews, ratings, and reputation scores aggregated from connected directories and review sites are exposed through a single normalized API surface, so you do not have to integrate each source individually.
Patient contact details and appointment records are handled with encrypted credential storage, scoped access, audit logging, and HIPAA-aligned controls on every read and write.
Yes. In addition to reads, the API supports writes such as creating bookings against provider availability and posting responses to patient reviews back to the originating directory.