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?
The documentation needs for API data products go beyond standard API mechanics and must explicitly support both data understanding and trust.
This category shines a spotlight on the distinct documentation requirements of data products delivered via APIs—particularly in contrast to operational APIs or microservices. The focus here is on data content, structure, provenance, and interpretability. While operational API documentation explains how to call a function, data product documentation must additionally enable clients to understand, trust, and effectively use the data itself. For API data products, users require a hybrid of technical API documentation and classic data dictionary or metadata documentation.
In this category, we recognize outstanding examples of API data product portals that empower clients to consume these information assets for decision-making, analytics, modeling, and more. A nominee might be a standalone portal or a dedicated section within a broader platform, specifically focused on the organization’s data products. Strong emphasis is placed on lifecycle management and on bringing information assets out of “dark data territory” into tangible business value.
Award Criteria
Key questions we’ll be asking judges and nominators:
- How do you expose your data products? Consumers need to fully grasp what data is available, what it means, and how to work with it.
- How do you communicate pricing strategies for a product that radically changes in value depending on its use case?
- How do you manage the different formats in which data can be used?
- Does the documentation help users assess the fitness for purpose, biases, and reliability? Is there transparency around coverage, accuracy, and known gaps? Is there clarity about schema changes, data updates, and deprecations?
- Does the data product come with regulatory, privacy, and licensing constraints? How do you help prevent legal risks and support responsible data use?
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!
