FreeStyle Libre API 2026: LibreView Integration Guide
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.

You cannot sign up for a public FreeStyle Libre API today. Abbott publishes no developer portal, no API terms and no price list. In practice you reach Libre data in one of three ways: Abbott's own Epic integration if your clinics run Epic, a named Abbott partner, or an aggregator that reads LibreView data through a clinic "practice" account. The rule that decides most projects is simple. If your patients can share their LibreView data with a practice you control, you can build in weeks. If you need a direct Abbott agreement, nobody outside Abbott can tell you the timeline.
Want a team to build this for you? Our medical device integration services cover the vendor approval, the data pipeline and EHR delivery, and our remote patient monitoring software work covers RPM programs.
FreeStyle Libre integration at a glance
| Question | Short answer |
|---|---|
| Is there an official public API? | No. No Abbott developer portal was found. |
| Cost to the developer | Abbott: not published. Junction needs its Scale plan for custom practices. |
| Does the end user need anything paid or specific? | A FreeStyle Libre sensor and a LibreView account. The Epic route covers Libre 3 and Libre 2 systems. |
| Same-day start? | Not with Abbott. Through an aggregator you can start once your plan and LibreView practice are set up. |
| Who approves scale-up? | Not published. Validic says customer apps need Abbott pre-approval and special licensing. |
| HIPAA and BAA | Abbott's stance is not published. Ask Abbott and your aggregator directly. |
| Raw or summary data? | CGM glucose readings, plus notes, carbs and insulin entries. Reading frequency is not published. |
| First build | 2 to 4 weeks through an aggregator practice route. Direct with Abbott is unknown. Both are our estimates. |
Integration strategies
| Route | Own mobile app? | Own server? | Vendor approval or contract? | SDK? | Latency | Supported data | Not supported | Best for |
|---|---|---|---|---|---|---|---|---|
| Abbott public cloud REST API | Does not exist publicly. No portal, scopes or terms found. | |||||||
| Abbott to Epic integration | No | No | You need Epic. It runs through Epic's Aura software. Abbott's setup steps for clinics are not published | No | "Automatically" per Abbott. No number published | Libre 3 and Libre 2 glucose data in Epic | Alarms (Abbott's release says the feature set excludes alarms) | Health systems on Epic |
| Named partner platform (Tidepool, Glooko) | No | Depends on the partner | Yes, with the partner. Terms not published | No | Tidepool says continuous and automatic | Glucose in the partner's platform | Not published | Clinics already using those tools |
| Aggregator, practice route (Junction freestyle_libre) | No | Yes | Aggregator plan (Junction Scale). Validic says Abbott pre-approval for its customers | No | Not published | CGM glucose, notes, carbs, insulin | Alarms, real-time streaming | RPM vendors and digital health apps |
| Aggregator, patient login (Junction abbott_libreview) | Closed to new organisations. Existing connections keep syncing. | |||||||
| Other aggregators | Thryve lists Libre as a cloud source through LibreView. Validic lists Abbott as restricted: it needs a direct relationship with Abbott and is US only. Validic says Abbott does not publish its developer terms. Spike lists it with no route stated. Terra and ROOK do not list it. Sahha coverage is not published. | |||||||
| Phone SDK, webhooks, file export | Not found in public docs. | |||||||
| Apple Health or Health Connect | Not published. Abbott documents no Apple Health or Health Connect writing for the Libre apps. Its sharing goes through LibreView and LibreLinkUp. | |||||||
| Unofficial LibreView endpoints | A community reference exists and states it is not affiliated with Abbott. Do not build a commercial product on it. | |||||||
For a healthcare buyer on Epic, ask your Epic team about Abbott's integration first. It is the only route Abbott itself announced. For an RPM vendor or a digital health product, the aggregator practice route is the fastest path you can actually start, as long as you clear the Abbott licensing question in writing. A fitness or sleep app has no easy route. The practice route is built for clinics, so a consumer app has to run a LibreView practice and still clear the same licensing question. No Apple Health or Health Connect route was found.
Each route in more detail
Abbott to Epic. Abbott announced this on 29 April 2025. Patients link their LibreView account to Epic, and data then flows into Epic automatically. It covers the FreeStyle Libre 3 and 2 systems. Abbott's own release says the feature set excludes alarms. You build nothing here, and you control nothing. The data lands in Epic. It does not reach a vendor product sold into that health system.
Named partners. Tidepool announced continuous, automatic Libre integration in the US in October 2024. A Glooko integration was reported in 2025. The terms of these partnerships are not published, so you cannot copy them. They are useful as proof that Abbott does sign data partners, and as an option if your clinics already use those platforms.
Junction practice route. Junction's provider freestyle_libre works through clinic sharing. You create a LibreView practice. Junction joins it as a practice member. Each patient shares their LibreView data with your practice using its Practice ID. Junction then reads the data and passes it to you. Your server receives it. No phone app is needed for the data to flow.
Junction patient-login route. The older provider abbott_libreview asked the patient for their LibreView login. Junction has closed it to new organisations. Existing connections keep syncing. Junction says that flow can take up to 60 seconds to connect and can break about once a year when passwords rotate.
Thryve and Validic. Thryve lists Libre among its supported devices. Validic's documentation says customer apps need pre-approval and special licensing from Abbott. We read only a search excerpt of that Validic page, so confirm it with Validic. Treat it as the most direct public statement of Abbott's gate.
Unofficial endpoints. A community GitHub project documents LibreView and LibreLinkUp endpoints and states it is not affiliated with Abbott. It shows the data exists in Abbott's cloud. It gives you no rights to use it. A commercial product built on it may break Abbott's terms and can stop working without notice.
Build it yourself, use an aggregator, or work with a partner
| Question | Build in-house | Wearable aggregator | Build with a partner (Nirmitee) |
|---|---|---|---|
| Whose Abbott access? | Yours. Abbott publishes no public API, so you need a direct agreement. | The aggregator's, through a LibreView practice you run | Yours. We set up the route in your accounts. |
| Licensing risk | You ask Abbott directly | Validic says Abbott pre-approval and special licensing apply | Same question. We help you put it to Abbott in writing. |
| Patient sharing | Your own flow, if Abbott agrees one | Patients share LibreView with your Practice ID | We build the enrollment steps and the first-reading check |
| Data model | Whatever Abbott gives you | The aggregator's schema | FHIR Observations for your EHR or remote monitoring stack |
| Other devices later | One new build per device | Many devices through one API | Same pattern reused across devices |
| Time to first real user | Unknown. Depends on an Abbott agreement. | Depends on the aggregator's onboarding | 2 to 4 weeks of build in our estimate, plus the Abbott licensing answer |
| Cost shape | Engineering time. Abbott fees not published. | Aggregator fee. Junction needs its Scale plan. | Project fee, scoped after a call |
What data you can get
| Data type | Granularity | History window | Push or pull |
|---|---|---|---|
| CGM glucose readings | Individual readings. Frequency not published | Not published | Pulled by the aggregator. How it reaches you depends on the aggregator |
| User notes | Timestamps are hourly | Not published | Pull |
| Carbohydrates | Per note, hourly timestamps | Not published | Pull |
| Insulin injections (rapid or long acting) | Per note, hourly timestamps | Not published | Pull |
| Glucose in Epic (Epic route) | Not published | Not published | Flows into Epic automatically |
All LibreView data uses a floating time basis. That means the times carry no fixed time zone, so you must decide how to place them.
Handling the data you get
- Glucose readings are the core. Store each reading with its value and the floating time as received, plus the patient's time zone from your own records.
- Notes, carbs and insulin come as user entries with hourly timestamps. Show them as "around this hour" on screens.
- Insulin entries say rapid or long acting. Keep that label, since a care team reads the two very differently.
- Because history, frequency and delay are not published, measure them in your pilot. Record the gap between a reading's time and when it reached your server.
What is inside one Libre glucose record
Abbott publishes no record format or field list for LibreView. This is what the public sources show, and what you have to measure yourself.
| Part of the record | What is known |
|---|---|
| Glucose value | A CGM reading from interstitial fluid. Units follow the account, mg/dL in the US. Reading frequency is not published. |
| Time | Floating time with no time zone. Store the patient's zone yourself. |
| Notes, carbs, insulin | User entries with hourly timestamps. Insulin is labeled rapid or long acting. |
| Device | Abbott says the Epic feed applies to FreeStyle Libre 3 and 2 systems. Device fields in the feed are not published. |
| Alarms | Not in the Epic feature set, per Abbott's release. |
What you cannot get
- No public Abbott API, scopes, rate limits or developer terms.
- No alarm data in the Epic feature set. Abbott's release footnote says so.
- No real-time streaming found in public docs.
- No phone SDK, webhooks or file export from Abbott found in public docs.
- No exact timestamps for notes. They are hourly.
- No published reading frequency, sync delay or history window.
- No new patient-login connections at Junction.
- No published Abbott OAuth, so you cannot let patients sign in to Abbott from your app on an official route.
- No published terms of the Tidepool or Glooko partnerships.
How to get access
- Pick your route. Epic customers talk to their Epic team about the Abbott integration. Everyone else picks an aggregator. Approver and wait time for the Epic route: not published.
- Sign up with the aggregator. Junction needs its Scale plan for custom practices.
- Ask Abbott, through the aggregator, whether your app needs pre-approval or a license. Validic says it does for its customers. Who approves and how long it takes: not published.
- Create a LibreView practice account.
- Invite the aggregator's practice email to that practice as Care Team Admin.
- Give patients your Practice ID. Each patient shares their LibreView data with your practice.
- Start receiving data through the aggregator's API.
From zero to your first FreeStyle Libre data in four steps
Abbott publishes no API request format, so there is no official request to show. These are the documented steps for the practice route.
- Open a LibreView Professional Account. Abbott says the clinic must set one up and turn on the Practice feature first.
- Connect your aggregator. Invite the aggregator's practice email as Care Team Admin, as its docs describe, and get the licensing answer in writing.
- Have one test patient share. Abbott documents two ways: the clinic sends an email invitation from LibreView, or the patient enters your Practice ID under My Practices in their LibreView Account Settings.
- Confirm the first reading. Pull it through the aggregator's API, check the units and the floating time, and record how long it took to arrive.
Terms you must know
Abbott publishes no API terms, so there are no section numbers to cite. Here is what that means clause by clause.
- Medical use: no published clause. Healthcare products must get Abbott's position in writing before launch. Wellness products face the same gap.
- PHI, HIPAA and BAA: Abbott's stance is not published. A healthcare product needs a BAA with its aggregator and an answer from Abbott on who holds the data. A wellness product should still treat glucose as sensitive data.
- Storage and retention: not published. Ask what you may keep after a patient stops sharing.
- AI training: not published. Do not train models on Libre data until you have it in writing.
- Display and branding: not published. Ask before you show the Libre name or logo.
- Data selling: not published. Assume you may not.
- Termination: not published. Validic's note on licensing suggests Abbott can control access. Plan for losing the feed.
- Competing products: not published. Ask if you build glucose tools that compete with LibreView.
- Aggregator terms apply on top. Read the aggregator's own contract for each point above.
Cost and payment terms
- Abbott developer fees: not published.
- Junction: custom practices require its Scale plan. The price is on Junction's side and is not in our research.
- End users need a Libre sensor and a LibreView account. Sensor pricing is out of scope here.
- Abbott licensing fees, if any: not published.
Use cases
1. Diabetes remote patient monitoring
The RPM vendor runs a LibreView practice linked to an aggregator. At enrollment the patient shares LibreView with that Practice ID. The aggregator reads new glucose readings and you receive them through its API. You store them, flag out-of-range values for the care team and write summaries to the EHR as FHIR Observations. Data used: glucose, insulin, carbs.
- Patient never completes sharing. Fix: walk them through it at enrollment and confirm the first reading arrives before they leave.
- Times look shifted. Fix: LibreView time is floating. Store the patient's time zone and apply it.
- Staff expect alarms. Fix: say up front that alarms are not in the feed and keep the patient's own Libre alerts.
2. Clinic glucose review in Epic
The patient links LibreView to Epic and readings flow into the chart. The clinician reviews them at the visit. Data used: Libre 3 and Libre 2 glucose.
- The clinic is not on Epic. Fix: use the aggregator route.
- The patient has not linked. Fix: add linking to the visit checklist.
3. Metabolic digital therapeutic or coaching app
The user shares LibreView with your practice. The app pulls glucose, carbs and notes and shows how meals relate to glucose on the app screen. Data used: glucose, carbs, notes.
- Abbott licensing blocks launch. Fix: get pre-approval in writing before you build.
- Meal timing is off by up to an hour. Fix: note timestamps are hourly, so let users log meals in your app too.
4. Clinical trial glucose endpoint
The site creates a LibreView practice and enrolls participants with its Practice ID. The aggregator delivers glucose to your trial database. Data used: glucose.
- History window is unknown. Fix: start sharing at enrollment and do not rely on back-fill.
- The feed stops mid-study. Fix: monitor last reading per participant daily and call the site when it goes quiet.
- Legacy password connections break. Fix: avoid them. Junction says they can fail about once a year from password rotation.
5. Fitness, sleep or performance app showing glucose
The user wears a Libre sensor and wants glucose next to sleep or workouts in your app. The only documented path is the practice route. You run a LibreView practice, the user shares with your Practice ID, and the aggregator passes readings to your server. Your app pulls them from your server. Data used: glucose, carbs, notes.
- Abbott licensing may not cover a wellness app. Fix: ask Abbott, through the aggregator, before you design the feature.
- Users find "share with a practice" odd in a consumer app. Fix: explain in the app that this is how LibreView sharing works.
- Readings arrive later than the user expects. Fix: delay is not published, so measure it in a pilot and show "last updated" on screen.
FreeStyle Libre data in an EHR or remote monitoring program
If your clinics run Epic, Abbott's own integration puts Libre glucose into the chart, and you map nothing. Abbott takes questions on it at Libre.Epic@abbott.com. For any other EHR or a remote monitoring platform, turn each reading into a FHIR Observation, the standard record for a measurement, and send it on.
| Libre value | FHIR resource | Code |
|---|---|---|
| CGM glucose, mg/dL | Observation | LOINC 99504-3, glucose mass/volume in interstitial fluid |
| CGM glucose, mmol/L | Observation | LOINC 105272-9, glucose moles/volume in interstitial fluid |
| Carbohydrates note | Observation | LOINC 9059-7, carbohydrate intake estimated |
| Insulin note, rapid or long acting | MedicationAdministration | Keep the rapid or long acting label. The note carries no product, so no drug code fits. |
Do not use the blood glucose codes for Libre readings. A CGM measures interstitial fluid, and the codes above say so. Store the patient's time zone with each Observation, since LibreView time is floating.
Known blockers and gotchas
- No public program. Abbott offers no self-serve API. Use Epic or an aggregator, and get the licensing answer in writing.
- Pre-approval. Validic says customer apps need Abbott pre-approval and special licensing. Treat this as a likely gate until Abbott says otherwise.
- Patient-login route closed. Junction no longer accepts new abbott_libreview connections. Use the practice route.
- Password flow is fragile. The legacy flow can take up to 60 seconds and can break about once a year. Do not build new work on it.
- Floating time. LibreView times carry no time zone. Store the patient's zone yourself.
- Hourly note times. Carbs and insulin notes carry hourly timestamps. Do not use them for dose timing.
- Epic only covers Epic. The Abbott to Epic feed helps health systems on Epic. Other EHRs have no announced Abbott route. Use an aggregator and write FHIR yourself.
- Partner terms are private. Tidepool and Glooko show Abbott signs partners, but you cannot see the terms. Ask Abbott for its partner process directly.
- Silent drop-off. If a patient stops sharing with your practice, we expect data to stop with no notice (our judgement, not documented). Alert on "no reading in 24 hours" per patient.
- Unofficial endpoints. Community code exists but is not Abbott's. It carries terms and stability risk.
Delivery timeline
Our estimate for the aggregator practice route. Direct with Abbott is unknown.
| Week | Work | Depends on vendor? |
|---|---|---|
| 0 | Aggregator plan and Abbott licensing answer | Yes, aggregator and Abbott |
| 1 | LibreView practice setup, invite aggregator as Care Team Admin, test patient shares | Yes, LibreView |
| 1 to 2 | Server, webhook handling, storage, time zone handling | No |
| 2 to 3 | FHIR mapping and EHR or app screens | No |
| 3 to 4 | Pilot with real patients, monitoring, support scripts | Partly, patient sharing |
Questions to ask before you sign
- Does our use need Abbott pre-approval or a license, and who at Abbott approves it?
- Will you sign a BAA, and does Abbott need one too?
- How often are readings available, and what is the delay from sensor to our server?
- How much history do we get when a patient first shares?
- Are alarms or events available anywhere?
- What happens to our feed if Abbott changes access, and how much notice do we get?
- May we store data after a patient stops sharing, and for how long?
- Are we allowed to use the Libre name on our screens?
Other device integration guides
Libre is often one device among several. Each guide below uses the same layout, so you can compare access, data and terms side by side. For the full service, see medical device integration.
- Oura API integration guide
- WHOOP API integration guide
- Garmin API integration guide
- Ultrahuman API integration guide
- Eight Sleep API integration guide
- Fitbit and Google Health API integration guide
- Apple Health API integration guide
- Health Connect API integration guide
- Samsung Health API integration guide
- Withings API integration guide
- Dexcom API integration guide
- Polar API integration guide
- COROS API integration guide
- Suunto API integration guide
- Strava API integration guide
- Peloton API integration guide
- MyFitnessPal API integration guide
Plan your Libre integration with us
Tell us your device, your users and your target date, and we will send back the route, the vendor approvals you need and a build plan. Plan your device integration.
For whoever builds this
- Abbott auth, endpoints, scopes, token rules, rate limits and webhook signing: not published.
- Junction practice provider slug:
freestyle_libre. Legacy patient providerabbott_libreviewis closed to new orgs. Setup: LibreView practice, invite Junction practice email as Care Team Admin, patients share by Practice ID. - Legacy password flow: up to 60 seconds, breaks about yearly on password rotation.
- Time: LibreView uses floating time. Note timestamps are hourly. Store patient time zone.
- FHIR: glucose as Observation, insulin as Observation or MedicationAdministration, carbs as Observation. Checked LOINC codes: 99504-3 interstitial glucose mg/dL, 105272-9 interstitial glucose mmol/L, 9059-7 estimated carbohydrate intake. Insulin has no single LOINC code that fits a logged dose, so model it as MedicationAdministration. Check the HL7 CGM implementation guide before go-live.
- Versions: Abbott to Epic announced 29 April 2025. Junction deprecation date not stated.
Sources
All read 10 November 2026, except the four Abbott pages marked 11 November.
- Abbott press release on Epic integration, re-read 11 November 2026 for the alarms footnote, Aura and contact: https://abbott.mediaroom.com/2025-04-29-Abbott-Integrates-Libres-Data-with-Epics-Electronic-Health-Record-System,-Providing-Healthcare-Professionals-Seamless-Glucose-Monitoring-Information
- Abbott, sharing LibreLink data with your doctor using LibreView, read 11 November 2026: https://www.freestyle.abbott/en-ae/support/how-do-i-share-freestyle-librelink-data-with-my-doctor-using-libreview-.html
- Abbott, LibreView product page, read 11 November 2026: https://www.freestyle.abbott/en-za/products/app-and-data-sharing/libre-view.html
- Abbott, Libre Assist and other health apps, read 11 November 2026: https://www.freestyle.abbott/en-us/support/faq/apps/libre-assist-integration-with-other-health-apps-and-devices.html
- NLM Clinical Tables LOINC search for 99504-3, 105272-9 and 9059-7, read 11 November 2026.
- Abbott on Libre Assist and health apps, https://www.support.freestyle.abbott/hc/en-us/articles/41650357929745-Can-Libre-Assist-integrate-with-other-health-apps-or-devices-like-Apple-Health-or-Fitbit, read 10 November 2026.
- Terra supported integrations, https://docs.tryterra.co/reference/health-and-fitness-api/supported-integrations, read 10 November 2026.
- Thryve data sources overview, https://docs.thryve.health/thryve-data-sources/overview, read 10 November 2026.
- ROOK data sources, https://docs.tryrook.io, read 10 November 2026.
- Sahha integrations, https://www.sahha.ai/docs/connect/integrations.md, read 10 November 2026.
- Spike integrations, https://www.spikeapi.com/integrations, read 10 November 2026.
- Validic supported devices and restricted vendor list, https://www.validic.com/features/supported-devices/, read 10 November 2026.
- Abbott press release on Epic integration, 29 April 2025: https://abbott.mediaroom.com/2025-04-29-Abbott-Integrates-Libres-Data-with-Epics-Electronic-Health-Record-System,-Providing-Healthcare-Professionals-Seamless-Glucose-Monitoring-Information
- Tidepool, Libre integration launch: https://www.tidepool.org/blog/abbott-freestyle-libre-integration-launched
- Junction FreeStyle Libre guide: https://docs.junction.com/wearables/guides/freestyle
- Thryve supported devices, Libre: https://www.thryve.health/supported-wearable-devices/abbott-freestyle-libre
- Validic documentation excerpt: https://validic.atlassian.net/wiki/x/FACT-w
- Community LibreView reference, not affiliated with Abbott (unofficial): https://github.com/FokkeZB/libreview-unofficial
- Medthority coverage of the Epic integration (secondary): https://www.medthority.com/news/2025/4/abbott-integrates-libres-data-with-epics-electronic-health-record-system-providing-healthcare-professionals-seamless-glucose-monitoring-information/
Ready to scale?
Talk to our healthcare engineering team about building, integrating, and shipping faster.
Frequently Asked Questions
Does Abbott have a public FreeStyle Libre API?
How do I get FreeStyle Libre data into Epic?
Can an aggregator like Junction get Libre data?
Do I need Abbott approval to use Libre data in my app?
What Libre data can I get?
Can a fitness or sleep app get FreeStyle Libre data?
Are Libre alarms available through integrations?
Why are my Libre timestamps off?
Can I still connect Libre patients with their LibreView password?
Does Abbott sign a BAA for Libre data?
How long does a FreeStyle Libre integration take?
How does a patient share LibreView data with my practice?
Which LOINC code should I use for Libre glucose?
Which Libre systems does the Epic integration cover?
Does Abbott offer webhooks or rate limits for Libre data?
Can the Libre app send glucose to Apple Health or Fitbit?
Who do I contact at Abbott about the Epic integration?


