How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

National Institutes of Health (NIH) Organelle API

#### Options to download RefSeq organelle genome data, including the associated sequence and metadata.These organelle services allow you to get RefSeq organelle genome metadata as a data report or download gene, transcript and protein sequence, and metadata, as an organelle data package, for RefSeq organelle genomes.

National Institutes of Health (NIH) Organelle API is one of 15 APIs that National Institutes of Health (NIH) publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Organelle. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 5 operations across 5 paths, and defines 31 schemas. It is described by OpenAPI 3.2.0, at version v2.

Requests are made against a single base URL, https://api.ncbi.nlm.nih.gov/datasets/v2.

5 operations 5 paths 31 schemas 3 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v2
Base URL
https://eutils.ncbi.nlm.nih.gov/entrez/eutils/
Authentication
API Key, API Key
Resource Areas
1

Authentication & Security 2

National Institutes of Health (NIH) Organelle API declares 2 security schemes for authenticating requests. An API key is passed in the query as api_key (ApiKeyAuth). An API key is passed in the header as api-key (ApiKeyAuthHeader). By default, every request must be authenticated.

Paths & Operations 5

Across 5 paths, the API surfaces 5 operations — 3 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Organelle 5

Options to download RefSeq organelle genome data, including the associated sequence and metadata. These organelle services allow you to get RefSeq organelle genome metadata as a d…

GET
/organelle/accession/{accessions}/download
Get an organelle data package by nucleotide accession
download_organelle_package 3 params → default200
POST
/organelle/download
Get an organelle data package
download_organelle_package_by_post 1 param body → default200
GET
/organelle/accessions/{accessions}/dataset_report
Get an organelle data report by nucleotide accession
organelle_datareport_by_accession 9 params → default200
GET
/organelle/taxon/{taxons}/dataset_report
Get an organelle data report by taxon
organelle_datareport_by_taxon 12 params → default200
POST
/organelle/dataset_report
Get an organelle data report
organelle_datareport_by_post body → default200

Schemas 31

The contract defines 31 schemas that model the data the API accepts and returns. The most detailed are v2OrganelleMetadataRequest (12 properties), v2reportsOrganelle (10 properties), v2reportsError (8 properties), v2reportsOrganism (8 properties). Each schema is shown below with its type and property counts.

v2SortDirection
string
v2reportsWarningGeneWarningCode
string
v2OrganelleSort
object
2 properties
v2reportsSequenceInformation
object
3 properties
v2reportsErrorGeneErrorCode
string
v2reportsWarning
object
5 properties
v2reportsLineageOrganism
object
2 properties
v2OrganelleMetadataRequest
object
12 properties
rpcStatus
object
3 properties
v2reportsOrganelleGeneCounts
object
5 properties
v2reportsError
object
8 properties
protobufAny
object
2 properties
v2reportsMessage
object
2 properties
v2OrganelleDownloadRequest
object
3 properties
v2reportsOrganelle
object
10 properties
v2OrganelleMetadataRequestOrganelleTableFormat
string
v2reportsWarningReplacedId
object
2 properties
v2reportsErrorTaxonomyErrorCode
string
v2reportsErrorAssemblyErrorCode
string
v2reportsOrganelleDataReports
object
4 properties
v2IncludeTabularHeader
string
v2reportsOrganelleType
string
v2reportsBioProject
object
4 properties
v2reportsErrorOrganelleErrorCode
string
v2reportsOrganelleBiosample
object
1 property
v2reportsInfraspecificNames
object
6 properties
v2reportsOrganism
object
8 properties
v2reportsOrganelleTopology
string
v2reportsErrorVirusErrorCode
string
v2OrganelleMetadataRequestContentType
string
v2AnnotationForOrganelleType
string

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

nih-organelle-api-openapi.yml Raw ↑

Other APIs National Institutes of Health (NIH) publishes across the network.

NCBI E-utilities (Entrez Programming Utilities)
PubChem Power User Gateway (PUG REST)
NIH RePORTER API
NCBI BLAST URL API
PubMed Central (PMC) OA API
National Institutes of Health (NIH) BioSample API
National Institutes of Health (NIH) Gene API
National Institutes of Health (NIH) Genome API
National Institutes of Health (NIH) Prokaryote API
National Institutes of Health (NIH) Stats API
National Institutes of Health (NIH) Studies API
National Institutes of Health (NIH) Taxonomy API
Where this information came from

This is an independent, third-party profile of National Institutes of Health (NIH) Organelle API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.