Does Kroll have an API? What actually integrates with Kroll in 2026

Pharmacy owners, IT consultants, and developers land on this question for the same reason: they want something outside Kroll to talk to Kroll. Usually that something is incoming prescriptions. Since PrescribeIT shut down on May 29, 2026, the question has come up a lot more, because the electronic feed that used to drop prescriptions into Kroll is gone and the faxes are back. Here is a plain answer based on what TELUS Health publishes and what is actually running in Canadian pharmacies.

The short answer

Yes, Kroll has an API. No, it is not a public, self-serve developer API that a third party can sign up for and use to write prescriptions into your dispensary. The Kroll API that TELUS documents is an internal integration layer between Kroll and TELUS’s own products, most visibly the Assyst Point of Sale system. Everything else that connects to Kroll does so through a TELUS partner arrangement, through a network Kroll was built to receive from (PrescribeIT, now shut down), or through automation that runs on the pharmacy workstation: either screen-level bots, or an agent that talks to Kroll directly under agreement, which is how AutoRx works.

What TELUS actually documents

The most concrete public document is the “Kroll API Integration User Guide” for Assyst Point of Sale, TELUS Health’s pharmacy POS system. It describes a live connection between the POS and Kroll that replaced an older text-file exchange. What it covers tells you what the API is for:

Scanning a filled prescription at the till and pulling every prescription in a work order with a single scan.
Third-party charges and end-of-day reports that reconcile against the Kroll Adjudication Totals report.
An “Unpaid Rx” report of prescriptions filled in Kroll but not yet rung through the POS.
A Kroll-side flag that controls whether patient names are returned to the POS at all (the “Return Personally Identifiable Patient Information to POS” setting).

That is a retail and reconciliation integration between two TELUS products. It is not a prescription-entry interface, and TELUS does not publish an equivalent guide for third parties to create or edit prescriptions.

The other public surface is the Kroll add-ons catalogue. TELUS lists its own Kroll-integrated modules (Workflow, FaxRx Cloud, Minor Ailments, PharmaConnect, Central Fulfillment, Central Data Repository, Enhanced RxSync, Electronic Medication Administration Record, and others) plus a short list of partner add-ons such as Domedic, Ezotech, and Kramer Compounds. Partners get in through TELUS, not through an open registration page.

TELUS does grant API access to vetted partners case by case. MAPflow, the minor-ailments assessment platform, announced a Kroll API integration in 2025 for pulling patient context into assessments, and Kroll release notes reference API modules such as eMAR consent management. Access runs through TELUS Health’s partner process and a business case, not a sign-up page.

How prescriptions used to get into Kroll electronically

Kroll’s electronic prescription intake was never a general API either. It came through PrescribeIT, the Canada Health Infoway network that TELUS Health built and that connected certified EMRs to certified pharmacy systems, Kroll included. PrescribeIT delivered structured prescription data into the Kroll workflow queue; Kroll did not expose that path to anyone else.

That network ended nationally on May 29, 2026. It survives only in Quebec, where the province is funding it as Prescription Québec (we cover the July 2026 agreement in PrescribeIT is back, but only in Quebec). Infoway has published a national e-prescribing open standard for vendors to adopt, but as of September 2026 no pharmacy-system vendor outside Quebec has announced a shipping implementation. So the electronic front door into Kroll is closed for most of the country, and the fax is the door that is open.

What “Kroll integration” means in practice today

If you strip away the marketing, there are five ways something connects to Kroll in 2026:

TELUS-built modules. FaxRx Cloud, Workflow, Minor Ailments, and the rest are Kroll features sold as add-ons. They integrate because TELUS owns both sides. FaxRx Cloud, for example, replaces the fax machine with a web inbox, but the prescription on that fax still has to be read and typed into Kroll by a person.
TELUS partner add-ons. A small set of vendors have a commercial and technical arrangement with TELUS. This is the route for a product that needs data access inside Kroll (compounding networks, medication management apps, security tooling). It is not something an independent pharmacy can arrange for its own project.
Reporting and exports. Kroll can produce reports and, in chain configurations, consolidate data into a central repository. Consultancies build reporting automation on top of these outputs. That is read-only and after the fact; it does not put prescriptions in.
Screen-level automation (RPA). Bots that operate the Kroll screens the way a technician would: open the patient, type the drug, sig, refills, and DIN, leave the prescription in the queue. Vision-based pharmacy bots work this way. It needs no API, but it is tied to screen layouts and it cannot read Kroll context before it types.
Agent-based integration under agreement. Software that runs a Kroll agent on the pharmacy’s workstation and talks to Kroll directly: it reads the patient profile and drug catalog first, then writes the prescription into the intake queue for verification. This is how AutoRx works. It is not the public API people search for, and it is not screen simulation either. It runs through supported interfaces under agreement, needs no schema work and no change request to TELUS, and can go live in about a week instead of a quarter.

Why intake automation does not wait for a public API

People sometimes assume anything short of a public API is a workaround. For prescription intake, the questions that matter are different.

It exists now. There is no third-party prescription-write API to wait for, and TELUS has no announced plan to publish one.
It uses Kroll’s own validation. Everything the agent writes goes through the same drug lookups, interaction checks, and plan adjudication that a technician’s entry would. Nothing bypasses Kroll’s rules.
The pharmacist stays in the loop. The prescription lands in the verification queue exactly as a manually entered one would. Nothing is dispensed on the automation’s say-so.
It survives Kroll updates. An agent that talks to Kroll directly is not tied to screen layouts; the vendor maintains the interface mapping. Your store does not carry an integration to support.
Patient data stays on site. Our deployment runs on premise inside the pharmacy network, with cloud used only to ship software updates, which matters for PHIPA, HIA, and PIPA obligations.

The honest limitation is throughput per workstation and the need to keep the automation vendor current on your Kroll configuration. In practice that means about 30 seconds per prescription and a short setup call, not a development project. The Kroll pharmacy automation guide covers the workflow, the compliance posture, and the vendors that offer it.

If you are evaluating vendors

Ask any vendor that claims a “Kroll integration” three questions:

Is this a TELUS partner API integration, a report-level integration, screen-level RPA, or an agent that talks to Kroll directly? Each is legitimate; they solve different problems, and only the last two put prescriptions in.
Does a prescription entered by your tool land in the pharmacist verification queue before dispense? If not, walk away.
Where does patient data live while the tool is working? On-premise and Canadian-hosted are the answers you want.

And if you came here hoping to build against a Kroll API yourself: the public documentation covers POS reconciliation, not prescription entry, and partner access runs through TELUS Health’s pharmacy team. For intake, the fastest path is still to automate the workflow you already have. If you want to see that on your own Kroll setup, book a 30-minute walkthrough.

Frequently asked questions

Is there a public Kroll API? No. TELUS Health publishes no general public Kroll API. The documented “Kroll API” is the integration between Kroll and TELUS’s Assyst Point of Sale, and partner API access is granted case by case after a business case.

How does AutoRx write prescriptions into Kroll without an API? Through a Kroll agent on the pharmacy workstation that reads the patient profile and drug catalog and writes the prescription into the intake queue directly, under agreement. It does not simulate clicks on the screen.

Can my pharmacy get Kroll API access for its own project? Not in practice. TELUS’s partner process is aimed at software vendors with a business case, not at individual stores.

Did PrescribeIT use the Kroll API? PrescribeIT delivered structured prescriptions into Kroll through the Infoway network that TELUS built and certified. That path closed nationally on May 29, 2026 and survives only in Quebec.

Sources

TELUS Health, “Assyst Point of Sale - Kroll API Integration User Guide” (public PDF, 27 pages)
TELUS Health, Kroll add-ons catalogue (telus.com/en/health/health-professionals/pharmacies/add-ons)
MAPflow, announcement of a TELUS Health Kroll API integration (2025)
AutoRx, Kroll integration page (getautorx.ca/integrations/kroll/)