What teams build with it
Every one of these starts with data your team already keeps current in EnrollPilot. The API just stops it from ending there.
Tap any use case to see how it works
Point Power BI, Tableau, Looker, or a scheduled Google Sheet at your enrollment data and the monthly status deck builds itself. How many providers are pending with which payers, how long the average case has been open, which markets are waiting on what. All of it refreshed on a schedule instead of assembled the night before the meeting.
What flows
When a new provider is entered in EnrollPilot, your HR platform, scheduling system, or staff directory can pick them up on its next sync: name, NPI, specialty, and which groups and locations they belong to. No one retypes a ten-digit NPI into a second system, and no one discovers the mismatch during an audit.
What flows
EnrollPilot already tracks every license, DEA, board certification, and document with a date on it. Pull the ones coming due and post them into Slack, Teams, or your ticketing system every Monday morning, so a lapsed credential is a task in someone's queue instead of a discovery made by a payer.
What flows
Land providers, groups, enrollments, and document metadata in Snowflake, BigQuery, Redshift, or plain Postgres, and join them to claims, scheduling, and revenue. That's how you finally answer the expensive question: which providers are billing under payers they aren't fully enrolled with yet.
What flows
What's available
The same records your team works in every day, structured for a machine instead of a screen.
Your full roster with specialties, contact details, identifiers, and the groups each provider belongs to.
Practice groups with their service locations, TINs, and group-level identifiers.
Every provider enrollment case with its payer, status, requirement checklist, and lines of business.
Group-level payer contracts, so entity-level agreements read the same way individual cases do.
Licenses, certifications, and documents approaching their expiration date. This is the feed behind any alert you want to build.
What's on file, for whom, and when it expires. Details only. The files themselves stay in EnrollPilot.
Getting started
Any admin in your organization can do the first two. The third is a single request your developer, analyst, or BI tool makes.
In EnrollPilot, go to Admin, then Organization, then API keys. Name it after wherever it will run, like "Power BI refresh" or "warehouse sync," so you always know what a key is for.
Tick only the data that tool needs. The key is shown once, right there in the dialog. Copy it into your secret manager, because we store only a hash and can't show it again.
Anything that can call a URL with a key attached can read your data: a BI connector, a scheduled script, an integration platform. First results come back in about a minute.
# everything that changed since your last sync curl "https://app.enrollpilot.com/api/v1/providers?updated_since=2026-07-01" \ -H "Authorization: Bearer epk_live_••••••••" { "data": [ { "name": "Jordan Reyes", "npi": "1234567890", "specialty": "Family Medicine", "isActive": true, "groupMemberships": [ { "name": "Northside Family Care" } ] } ], "nextCursor": "MjAyNi0wNy0xOVQxMzo0NDow…" }
Ask for everything that changed since your last run, page through the rest, and you have a sync. That's the pattern for all six resources.
Straight answers
Not today. Version one reads only, which is what makes it safe to hand to a reporting tool. If two-way sync is what your project needs, tell us. It shapes what we build next.
As fresh as you ask for it. Your integration decides how often it checks, whether that's hourly, nightly, or every fifteen minutes, and each run only pulls what changed since the last one.
Yes. Your organization can make 600 requests a minute, each returning up to 200 records, far more than a nightly sync of even a very large roster needs.
For a BI connector or an integration platform, usually not. For a custom sync, someone technical writes it once and it runs on its own. We're happy to get on a call with whoever builds it.
No. You can see what documents exist and when they expire, but the files themselves stay in EnrollPilot where access is logged and controlled.
Organization admins only, from inside EnrollPilot. Creating and revoking keys is recorded in your audit log, and every key's usage is visible on the same page.