DrugBank sells its full database under license, and that is where we start: your licensed XML becomes clean tables, every release gets a diff, and the open drug data around it is joined in.
Plans from €169 a month · Free project assessment · Reply within 1 business day
CSV · Excel · JSON · XML · FTP · SFTP · Amazon S3 · Google Cloud
API, JSON feed or CSV, XLSX and JSON files
ScheduleOne-time, monthly, weekly, daily or 3 times a day
DrugBank pages, filters, fields and a schedule
Built, monitored and repaired by our team
API, JSON feed or CSV, XLSX and JSON files
We collect the public drug cards on your schedule, and where you already hold a DrugBank release, the file lands in your bucket or our job runs in your environment. We extract DrugBank data from the XML into tables for drugs, synonyms, products, interaction pairs, proteins, pathways and identifiers, diff each release against the one before, and deliver CSV, Parquet, SQL or an API endpoint we host or run inside your own cloud. Around it we collect FDA labels, RxNorm, ChEMBL, PubChem, UniProt and trial registries and join them on UNII, InChIKey, RxCUI and UniProt IDs.
Where a source is guarded, DrugBank included, we bring anti-bot handling, proxy rotation and CAPTCHA solving, and we never sign in. Nothing here touches personal data: these records describe molecules, proteins and products, not people.
A DrugBank drug record is one entry described by the drugbank.xsd schema. Each drug carries a type of small molecule or biotech, created and updated dates, and a primary drugbank-id of DB plus five digits, followed by secondary IDs left by merged entries and older formats such as APRD, BIOD, BTD, EXPT and NUTR. Salts get DBSALT IDs and metabolites DBMET IDs.
Identity. Name, description, CAS number, UNII, average and monoisotopic mass, physical state, groups (approved, investigational, experimental, withdrawn, illicit, nutraceutical, vet_approved), synonyms tagged by language and coder, international brands with their company, mixtures, salts, a chemical taxonomy from kingdom to direct parent, categories with MeSH IDs, ATC codes that carry all four parent levels, and AHFS codes.
Pharmacology. Indication, pharmacodynamics, mechanism of action, toxicity, metabolism, absorption, half-life, protein binding, route of elimination, volume of distribution and clearance arrive as curated prose, not numbers. Calculated properties add logP, logS, pKa, polar surface area, SMILES, InChI, InChIKey and Rule of Five; experimental ones add melting point, water solubility and caco2 permeability.
Proteins. Targets, enzymes, carriers and transporters share one shape: name, organism, actions such as inhibitor or substrate, a known-action flag of yes, no or unknown, references, and a polypeptide with UniProt ID, gene name, cellular location, Pfam and GO terms and sequence. Enzymes add inhibition and induction strength. Pathways carry SMPDB IDs, reactions map a parent compound to its metabolite with the enzyme responsible, and SNP effects carry rs-ID, allele and PubMed ID.
Interactions and market. A drug-interaction is a partner DrugBank ID, its name and one sentence of description; food interactions are short advice lines. Products list labeller, NDC, DPD and EMA codes, marketing dates, dosage form, strength, route, FDA application number and generic or OTC flags, beside prices with currency, patents with expiry and pediatric extension, and external identifiers for PubChem, ChEMBL, ChEBI, KEGG, PharmGKB, BindingDB, ZINC and RxCUI.
The ScrapeIt DrugBank API serves the tables we build - drugs, synonyms, products, interaction pairs, proteins, pathways and identifiers - as JSON from an endpoint we host, refreshed on the schedule you set, or from inside your own cloud. Access to the endpoint is by key, and documentation of every field comes with the dataset.
Every table is keyed on the primary DB accession. Interaction pairs arrive as an edge list with the partner DrugBank ID, its name and the description sentence, and targets carry their UniProt accessions, so the same data joins outward on UNII, InChIKey, RxCUI and UniProt IDs. It also comes as CSV, Parquet, SQL or XLSX files, or as a load straight into your database.
Plans start from EUR 169 a month, or EUR 199 for a one-time extract, and a sample can be ordered before you commit.
DrugBank is a drug and drug-target knowledgebase that began at the University of Alberta and is run today by OMx Personal Health Analytics Inc., a Canadian company trading as DrugBank. A DrugBank dataset ties each molecule to the proteins it acts on, the pathways it runs through, the drugs it interacts with and the products it ships in, all under one DB accession number.
Signed out, go.drugbank.com shows a public drug card at addresses such as /drugs/DB01076: name, groups, type, summary, mechanism, the opening of the primary indication, formula and weight, first approval by country, synonyms, code names, brands, identifiers from UNII and CAS to ChEMBL, PubChem, RxNorm and ATC, InChIKey, SMILES, and targets and transporters as UniProt accessions. Enzymes and carriers stay hidden, and interactions, trials, indications, contraindications, products and references show only as counts.
Every card sits under its DB accession number, and the identifiers on it - UNII, CAS, InChIKey, RxNorm, ATC and UniProt accessions - are the keys that join a DrugBank dataset to the rest of your data.
Delivery: CSV, JSON or XLSX files, our API or a JSON feed. MCP server on request.
Full plan detailsBuyers fall into four camps. Pharma and biotech teams use DrugBank data for target identification, repurposing and due diligence on drug assets. Bioinformatics groups build drug-target networks from the protein blocks. Machine learning teams train interaction and binding models. Clinical software vendors need medication search, interaction checks and allergy cross-sensitivity inside an EHR or a telehealth app.
The DrugBank DDI dataset is where most confusion starts. In the XML an interaction is a pair of IDs plus one sentence, with no severity field; the sentences follow a small set of templates, which is why DDI prediction work often turns them into interaction-type labels.
Releases need discipline. Versions follow MAJOR.MINOR.PATCH: a major bump means an incompatible schema change, a minor one new data, a patch every new export, and releases are kept by version, so a model or a paper can pin 5.1.22. Merged entries survive as secondary IDs, so joins must resolve old accessions to the primary one before a diff between two releases means anything.
It is also why a DrugBank scraper keys every pass over the public drug cards on the primary DB accession, so name, groups, synonyms, identifiers and target accessions can be diffed against the pass before.
Learn how to use web scraping to solve data problems for your organization
Data scraping is the wide term that includes documents, scans and old screens; web scraping is the part that works on websites. We compare sources, daily work, output and cost drivers, give a briefing checklist and walk through two of our projects.
Leveraging advances in technology, the AI-powered web scraper has skyrocketed in demand and is helping to expand capabilities by automating tedious daily tasks and speeding up data collection from thousands of websites several times over.
Web scraping is a method of obtaining web data by extracting it from pages of web resources with the help of a program, that is, in automatic mode. It is used to syntactically convert web pages into more usable forms.
ScrapeIt works as your outsourced data team: we design the parsers and collectors, run them on your release calendar, and keep them working when a schema, a registry or a label format changes. Before we open a file you hold we sign a non-disclosure agreement.
ScrapeIt has no tie to DrugBank or OMx, and every pipeline we build can run inside your own cloud.
Still unsure? Write to info@scrapeit.io
Yes. The ScrapeIt DrugBank API returns name, groups, mechanism, synonyms, brands, identifiers and target accessions as JSON from an endpoint we host, refreshed on the schedule you set. The same data also comes as CSV or XLSX files or straight into your database. Access is by key, and plans start from EUR 169 a month, or EUR 199 for a one-time extract.
Yes. We deliver DrugBank data as CSV, JSON, XLSX, Parquet or SQL: drugs, synonyms, brands, identifiers and target accessions as separate tables keyed on the primary DB accession. If you already hold a DrugBank release file, we flatten it into CSV or Parquet on the same schema.
Everything the release carries, split into tables: the drug with its primary and secondary IDs, groups, synonyms, brands, taxonomy, ATC and MeSH categories and pharmacology prose; products with NDC, DPD and EMA codes; interaction pairs; food interactions; targets, enzymes, carriers and transporters with UniProt IDs and actions; pathways, SNP effects, patents and properties. Joins run on UNII and CAS for regulators, InChIKey for chemistry, RxCUI for clinical vocabularies and UniProt for proteins.
Every export raises the patch number. The current release, 5.1.22, came out on 27 June 2026, and its notes read no significant changes; a minor bump would signal new data and a major one a schema change, which is the event that breaks parsers. Releases are kept by version, so you can pin one for a paper or a model. We diff each release against the previous one - new accessions, merged IDs, added or dropped interactions, changed product rows - and deliver the change set with the full snapshot.
Yes. We collect the public drug card - name, groups, type, mechanism, synonyms, brands, identifiers and target accessions for each DB number - and never sign in. We collect only publicly available data - everything a visitor can see on DrugBank - and we collect it legally. Nothing here touches personal data: these records describe molecules, proteins and products, not people.
You share your needs, expectations, and desired timeframe. We'll suggest the best solution based on your request and budget.
Our specialists configure the crawlers and extract a sample dataset for your review before proceeding with the full-scale extraction.
Once you approve the sample, we launch the project and start full data collection. We gather, filter, and structure the data for easy use, delivering it on time in your preferred format.
Our team manages ongoing processes, monitors website changes, and supports all data extraction cycles. We can also help integrate data into your systems or create dashboards to simplify analysis.
Tell us which sites, which fields and how often. A couple of lines is enough to start.
DrugBank data from €169/month. Free project assessment, reply within 1 business day.