Welcome to the interactive reference for the HortiAPI OpenAPI definitions. This site renders the API design authored and maintained in the HortiAPI/HortiAPI repository, where the schema, resources, and implementation guidelines are collaboratively developed. Use the links below to explore endpoints, schemas, and examples for each version.
Supports the Linnaeus model for standardized flower & plant classification. Linnaeus provides a rigorously defined ontology for horticultural entities—distinguishing fixed taxonomic attributes (genus, species) from variable transactional data (inventory, pricing). By aligning with this industry‑recognized standard, HortiAPI ensures that data exchanged among growers, exporters, wholesalers, and service providers remains interoperable and unambiguous, reducing integration effort and preventing misclassification across the supply chain.
Each version’s viewer provides:
For C#/.NET consumers and servers, HortiAPI publishes these NuGet packages:
| Package | Contents |
|---|---|
HortiApi.Models |
Shared data models (DTOs) for client and server |
HortiApi.Resources |
Well-known resource string definitions |
HortiApi.Client.Rest |
Client implementation for HortiAPI endpoints |
HortiApi.Server |
Abstract ASP.NET 8.0 server base classes |
Import the OpenAPI file into your tool of choice:
Use definitions/hortiapi-v3-rc.14.yaml for the latest.
See the API in action with these practical example scenarios. These include:
The v3 schema references shared resource. These include:
These standardized identifiers ensure semantic consistency across all implementations.
HortiAPI uses structured error responses (RFC7807 Problem Details) that reference these standardized error types. These include:
For issues or questions on the spec itself, open an issue in the main API repo: HortiAPI/HortiAPI.