This article was accepted into the corpus but its outbound wikilinks were never NER-processed — typical at the deepest BFS hop or when the run's entity cap was reached. No expansion funnel to show.
| Entrez Programming Utilities | |
|---|---|
| Name | Entrez Programming Utilities |
| Developer | National Center for Biotechnology Information |
| Released | 1990s |
| Latest release version | N/A |
| Operating system | Cross-platform |
| Genre | Web API, Bioinformatics |
Entrez Programming Utilities provides a programmatic interface to query and retrieve data from the National Center for Biotechnology Information's integrated retrieval system. It enables automated access to records across databases such as PubMed, GenBank, Protein Data Bank, and ClinicalTrials.gov; supports bulk retrieval, linking, and metadata queries; and is widely used in pipelines developed by researchers at institutions such as the Broad Institute, Wellcome Trust Sanger Institute, European Bioinformatics Institute, and laboratories at universities including Harvard University, Stanford University, and Massachusetts Institute of Technology.
Entrez Programming Utilities are a suite of HTTP-based endpoints maintained by the National Center for Biotechnology Information to facilitate automated retrieval from curated resources like PubMed Central, PubMed, Gene, Genome, Structure, Taxonomy, OMIM, and dbSNP. The utilities underpin workflows in projects at organizations including National Institutes of Health, Centers for Disease Control and Prevention, World Health Organization, and collaborative efforts such as the Human Genome Project. They complement other programmatic services from bodies like the European Molecular Biology Laboratory and integrate into pipelines used by consortia such as the 1000 Genomes Project and initiatives at the Cancer Genome Atlas.
Key endpoints include search, fetch, summary, link, and spell-check capabilities that map to operations familiar in systems like Elasticsearch and Apache Solr but optimized for NCBI datasets. Prominent utilities mirror actions used in web services at institutions including European Bioinformatics Institute and Protein Data Bank, and they are analogous to RESTful APIs provided by organizations such as Google, Microsoft Research, and Amazon Web Services for large-scale data access. Specific functions support coordinated use with resources like RefSeq, UniProt, KEGG, Reactome, and external identifiers used by CrossRef and DataCite.
Requests are built as HTTP GET or POST calls and accept parameters similar to those used in APIs from entities such as GitHub, Twitter, and the Internet Archive. Responses are returned in structured formats including XML and JSON, facilitating parsing by libraries developed by groups like GNU Project, Python Software Foundation, Apache Software Foundation, and language ecosystems supported by Oracle Corporation and Microsoft. Metadata fields map to established identifiers from systems such as Digital Object Identifier, PubMed Identifier, and accession systems used by GenBank and RefSeq.
Access policy is enforced by the National Center for Biotechnology Information with guidelines comparable to rate-limiting frameworks used by Google Cloud Platform and Amazon Web Services. Users are encouraged to supply API keys associated with accounts at institutions like National Institutes of Health to increase request quotas; these practices align with API key models used by GitHub, Twitter, and Stripe. Usage policies reference compliance and citation norms followed by publishers such as Nature Publishing Group, Elsevier, and Wiley-Blackwell and by repositories like PubMed Central and Zenodo.
Researchers employ these utilities to automate literature searches in PubMed, bulk-download sequences from GenBank for analyses affiliated with projects at Broad Institute and Sanger Institute, and to cross-reference variant annotations with dbSNP in clinical studies at institutions such as Mayo Clinic and Johns Hopkins University. Bioinformatics toolchains integrate calls into workflows managed by systems like Nextflow, Snakemake, and Galaxy; developers embed utilities into platforms maintained by groups such as Bioconductor and Open Targets. Example tasks include harvesting abstracts for natural language processing used in collaborations with labs at Allen Institute for AI and building citation networks similar to services offered by Scopus and Web of Science.
Error handling follows patterns common in web APIs from organizations like Google, Microsoft, and Amazon: interpret HTTP status codes, implement exponential backoff for transient failures, and validate responses against schemas used by projects such as OpenAPI Initiative and W3C. Best practices include caching results as practised in infrastructures by European Bioinformatics Institute and using identifier resolution strategies employed by CrossRef and DataCite. For reproducibility, teams at Stanford University, Harvard Medical School, and Cold Spring Harbor Laboratory recommend logging requests, versioning queries, and attributing data sources in publications to publishers like Nature, Science, and PLOS.
Client libraries and wrappers are provided by communities and organizations including Bioconductor, the Python Software Foundation ecosystem (modules maintained by developers at Enthought and Anaconda, Inc.), and packages in language registries such as CRAN and npm. Integrations appear in platforms from Illumina and PacBio for sequencing data handling, and in visualization tools developed by teams at Broad Institute and EMBL-EBI. Third-party services and enterprise platforms like F1000Research and Benchling incorporate these utilities into research data management and annotation pipelines.