The Plants Database API provides access to extensive data on over 100,000 plant species, meticulously cleaned and sourced directly from the United States Department of Agriculture (USDA). The API is structured according to the OpenAPI 3.0.3 specification, making it easy to understand and integrate into various platforms.
OpenAPI Documentation:
https://plants-api-docs.netlify.app/
Extensive data on a variety of plant species, including their scientific and common names, symbols, family, and more.
Various endpoints allowing users to retrieve details, rarity status, growth habits, and state-based data for plants.
Support for filtering to enable users to find exactly what they are looking for.
API Endpoints
Retrieve Plants
Endpoint: /plants
Method: GET
Description: Retrieve a list of plants based on specified search parameters such as id, symbol, scientific name, and common name.
Paremeters: id, symbol, scientific_name, common_name, limit, offset
Retrieve Plant Details
Endpoint: /plants/details
Method: GET
Description: Retrieve detailed information for specific plants using various search parameters.
Paremeters: id, symbol, limit, offset
Retrieve Plant Rarity
Endpoint: /plants/rarity
Method: GET
Description: Retrieve information on the rarity status of specific plants.
Paremeters: id, symbol, scientific_name, common_name, rarity, limit, offset
Retrieve Plant Growth Habit
Endpoint: /plants/growth_habit
Method: GET
Description: Obtain data regarding the growth habits of specific plants.
Paremeters: id, symbol, scientific_name, common_name, growth_habit, limit, offset
Retrieve Plant States
Endpoint: /plants/states
Method: GET
Description: Get state-based data of plants using specified search parameters.
Paremeters: id, symbol, scientific_name, common_name, fips_code, limit, offset
Responses
Responses are structured uniformly across endpoints, containing:
data: An array of requested objects, each object adhering to its schema.
offset: The offset for the returned data.
limit: The limit for the returned data.
Schemas
Each endpoint refers to a specific schema to ensure data consistency (refer to OpenAPI Documentation for further details):
- Plant
- PlantDetails
- PlantRarity
- PlantGrowthHabit
- PlantState
Error Handling
The API responds with appropriate HTTP status codes and messages to indicate the success or failure of a request, for example, 400 for Invalid parameters supplied and 404 for Plant not found.
Contact
For any queries or issues related to the API, please contact tuvshno@gmail.com.
Conclusion
The Plants Database API offers a rich set of data on various plant species, ensuring ease of access and flexibility in data retrieval with well-defined endpoints, parameters, and consistent response structures. Whether you are a botanist, a developer, or simply a plant enthusiast, this API opens the door to a world of possibilities in exploring the fascinating realm of plants.