Structured Species Data
Built for Developers
Access curated, machine-readable species datasets through simple REST APIs designed for websites, applications, research tools, educational platforms, databases, and data-driven products.
Real species records.
Structured for software.
SpeciesAPI is built around a simple idea: information that can be explored by people should also be usable by software.
Our API datasets transform curated SpeciesAPI records into predictable machine-readable JSON, allowing developers to work with taxonomy, geographic origin, biological traits, cultivation information, uses, and dataset-specific attributes without scraping webpages.
Each API remains connected to its corresponding human-readable SpeciesAPI records, giving developers both structured data and contextual source pages.
Explore SpeciesAPI datasets
Each SpeciesAPI product is designed around the fields that actually matter for that group of organisms instead of forcing unrelated species into one generic schema.
Chili Peppers API
Structured chili pepper cultivar and species data for developers, covering taxonomy, Scoville heat, geographic origin, genetics, pod characteristics, flavor and aroma, cultivation traits, culinary uses, preservation and more.
Data designed for applications
SpeciesAPI datasets expose meaningful structured fields rather than forcing developers to extract important information from article text.
Taxonomy & identity
Scientific names, species, cultivars, families, alternate names, classifications and other identifying information.
Origins & genetics
Geographic origins, regions, heritage information, breeding history, genetic relationships and hybrid status where documented.
Biological traits
Dataset-specific physical and biological characteristics such as morphology, colors, growth traits and other observable attributes.
Cultivation data
Growth habits, sun requirements, cultivation characteristics and horticultural information where reliable structured data is available.
Uses & suitability
Culinary, horticultural, preservation, commercial, research and other documented applications depending on the dataset.
Source records
API records remain connected to human-readable SpeciesAPI pages so developers can inspect the context behind the structured response.
Simple endpoints.
Predictable JSON.
SpeciesAPI uses straightforward REST endpoints that can be integrated into websites, mobile apps, research tools, educational software, internal databases and other developer workflows.
Authenticated products use API keys sent securely through request headers.
GET /wp-json/speciesapi/v1/peppers GET /wp-json/speciesapi/v1/peppers/carolina-reaper Authorization: Bearer YOUR_API_KEY
Human-readable records and machine-readable data
SpeciesAPI does not treat the API as an isolated database. The structured dataset remains connected to the public SpeciesAPI encyclopedia so developers can understand where a record fits, inspect its context, and compare the API output with its human-readable page.
Focused datasets instead of one generic schema
Different organisms require different data models.
Chili peppers need fields such as Scoville heat, pod traits and culinary uses. Another plant dataset may require entirely different botanical or horticultural fields.
SpeciesAPI can therefore grow dataset by dataset while keeping each API useful, understandable and appropriate for the species it represents.
A growing library of specialized APIs
SpeciesAPI is expanding one structured dataset at a time. New APIs can be added here as their records, schemas and developer access are prepared for production use.
Structured chili pepper cultivar and species records with taxonomy, heat, origins, plant traits and other specialized fields.
Additional plant and species datasets can be introduced as their structured records and API schemas are completed.
Explore the first SpeciesAPI developer dataset
See how a detailed human-readable chili pepper record becomes structured, developer-ready JSON through the Chili Peppers API.