Developer portals for API data products
An operational API can often be understood by explaining its interface. A data product cannot. Understanding how to retrieve the data is only the beginning; people also need to understand what the data represents, where it comes from, how it should be interpreted, and whether it is appropriate for the decision they are about to make.
As data becomes more valuable, context becomes part of the product.
That context extends well beyond technical API documentation. Ownership, semantics, lineage, freshness, quality, licensing, compliance, intended use, and limitations are not supplementary information. Together, they allow people to develop confidence in the data they are about to consume and understand the responsibilities that come with using it.
This is what makes API data products distinct from operational APIs or microservices. An operational API primarily exposes behaviour. A data product exposes information assets whose value depends as much on their meaning as on the interface through which they are delivered. Developer portals therefore have a broader role to play: bringing together technical documentation, metadata, business meaning, and governance into a coherent experience.
The Best Developer Portal for API Data Products category recognises portals that meet this broader challenge. Whether presented as a dedicated portal or as part of a wider developer platform, the jury will be looking for experiences that help people understand not only how to access a data product, but also how to interpret it, use it responsibly, and develop confidence in the information it provides.
How do you expose your data products?
This category recognises developer portals that help people understand, evaluate, and confidently use API data products. Beyond making data accessible, the experience should communicate the context that allows consumers to interpret the information correctly, assess whether it is fit for purpose, and understand the responsibilities that come with using it.
A nominee may be a dedicated data portal or a section within a broader developer platform. The jury will be looking for experiences where technical documentation, metadata, business meaning, and governance work together to make data products genuinely usable. The strongest submissions help organisations bring valuable information assets out of “dark data” territory by making them understandable and trustworthy.
Award Criteria
Key questions we’ll be asking judges and nominators:
- How does the portal help people understand the data product? Can consumers understand what the data represents, how it is structured, its intended use, and its limitations, not only how to access it?
- How does the portal help consumers decide whether the data is fit for purpose? Does it communicate provenance, ownership, lineage, freshness, quality, coverage, known gaps, biases, or other information that helps establish confidence?
- How are the conditions for using the data communicated? Consider licensing, pricing, regulatory obligations, privacy, compliance, and permitted use.
- How well does the experience support the data product throughout its lifecycle? Are updates, schema changes, versioning, deprecations, and other changes communicated in ways that help consumers maintain confidence and adapt their use of the data?
- How successfully does the portal bring together technical documentation, metadata, business meaning, and governance into one coherent experience?
Nominate Now!
If your developer portal helps users unlock the power of data—by making it trusted, transparent, and easy to work with—we want to hear from you!
