Scriptline turns public, pharmacy-level dispensing figures into JSON. Benchmark a branch, build the items history for an acquisition target and check MHRA alerts across the estate, without clicking through one pharmacy at a time.
Example recall notice: one batch, pharmacy-level action
Scriptline
ref EX-2026/000 · simulated
Simulated data. Pharmacy names, items and the alert shown are invented for illustration.
The figures are public. The work of getting them into one sheet, every month, for every branch and every target, is what eats the week.
Fourteen branches, three or four neighbours each. That is fifty-odd pharmacy pages to open, read and copy before you can say which branches are losing ground locally.
With Scriptline: loop your ODS codes through the dispensing trends and area leaderboard endpoints and land the lot in one table.
The sales memo quotes an items figure. Checking it means rebuilding two years of monthly items in a spreadsheet, then doing it again for the comparables.
With Scriptline: pull the target's profile and monthly trend in one call each, and screen a whole area before you request the pack.
MHRA alerts arrive by email to whoever signed up. Across a group, nobody can say with confidence which branches have seen which notice.
With Scriptline: read the alerts list on your own schedule and post new notices to the channel every branch manager already watches.
Each endpoint is a hosted function. When you call it, we open the public source in a real browser on our side and return what it shows as JSON.
The core of Scriptline for pharmacy groups, brokers and buying groups: who dispenses what volume, where they rank, and what the MHRA has published.
Nine sources, 29 endpoints. We would rather show you exactly what exists than a logo wall. Need a source that is not here? Ask us.
No scraper to maintain and no browser to run. If your analyst can write a spreadsheet macro, they can call this.
Scriptline is a request API: data is read when you call. It is not a push stream, and it is as current as the public source is on the day.
# Dispensing trends for one pharmacy curl -L -X POST \ "https://api.notte.cc/functions/$FUNCTION_ID/runs/start" \ -H "Authorization: Bearer $KEY" \ -H "Content-Type: application/json" \ -d '{ "function_id": "'"$FUNCTION_ID"'", "variables": { "ods_code": "FZZ99", "months": 12 } }'
// Illustrative response shape. Field names and values are examples. { "status": "completed", "result": { "pharmacy": { "ods_code": "FZZ99", "name": "Hollowmere Pharmacy (example)", "area": "Example ICB area" }, "monthly_items": [ { "month": "2026-06", "items": 8190 }, { "month": "2026-07", "items": 8060 }, { "month": "2026-08", "items": 7980 } ], "area_rank": 4, "area_pharmacies": 12 } }
import os, requests FUNCTION_ID = os.environ["FUNCTION_ID"] KEY = os.environ["KEY"] branches = ["FZZ99", "FZZ98", "FZZ97"] # your ODS codes for ods in branches: r = requests.post( f"https://api.notte.cc/functions/{FUNCTION_ID}/runs/start", headers={"Authorization": f"Bearer {KEY}"}, json={ "function_id": FUNCTION_ID, "variables": {"ods_code": ods, "months": 12}, }, timeout=180, ) r.raise_for_status() print(ods, r.json())
Move the slider to your branch's monthly items and pick the kind of area it trades in. This is the view the area leaderboard endpoint lets you build for every branch you own or want to buy.
Simulated area. Every pharmacy name and figure here is invented. Real calls return the public, pharmacy-level figures the source shows on the day.
I used to spend the first two days of every month copying items figures into the board pack. Now the sheet refreshes itself and I spend that time working out why a branch slipped.
When a listing comes in I can have the target and every pharmacy around it in one table before the first call with the vendor. It changes the questions we ask.
The alerts feed into the same channel our branch managers use for everything else. I stopped forwarding emails and hoping somebody had read them.
For product and pricing teams in India, the Gulf and South Africa: read retail medicine listings across e-pharmacies through the same API, one search per call.
Every plan includes all 29 endpoints. You pay for runs, which is one call to one endpoint.
For a small group checking its own branches each month.
For 5 to 50 branches benchmarking every branch against its neighbours.
For brokers, buying groups and e-pharmacy pricing teams.
Prices exclude VAT. Cancel any time before the next billing month.
No. Everything returned is public, aggregate, pharmacy-level data: for example a pharmacy's total dispensed items in a month, or its position in an area ranking. There is no patient data, no prescriber-level data and nothing that identifies an individual.
From the nine public sources listed in the coverage section. When you start a run, we open the source in a real browser on our side, read what it publishes and return it as JSON. We do not alter the figures, and we name the source for every endpoint.
It is a request API. Data is read at the moment you call, so you get what the source shows on that day. Dispensing figures follow the source's own publication schedule, so the latest month available is whatever has been published. There is no push stream: if you want a daily alert check, you schedule a daily call.
No. Scriptline is an independent commercial service. It is not affiliated with, endorsed by or operated on behalf of the NHS, the MHRA, any regulator or any of the named sources.
Treat it as an input that saves you the manual collection, not as the final word. For an acquisition you will still do your own due diligence against the vendor's records. For recalls, keep your official MHRA subscription and your existing procedures: Scriptline helps you see and share alerts, it does not replace your obligations.
The endpoints read live websites, so a run can fail when a source is down or has changed. Maintaining the endpoints when a source changes is our job rather than yours. We do not publish availability figures on this page and would rather you test the endpoints you need before you depend on them.
An API key and anything that can send an HTTPS request: Python, Power Query, a no-code automation tool or a scheduled script. The Group plan includes a starter spreadsheet and notebook so an analyst can begin with a list of ODS codes.
No. Catalogue and price endpoints return what a retailer or reference site lists publicly. They are for product, pricing and market analysis and are not medical, clinical or prescribing advice.
Start with your own ODS codes and the pharmacies around them. The first benchmark table usually takes an afternoon, and then it refreshes whenever you ask.