-
openapi-directory
🌐 Wikipedia for Web APIs. Directory of REST API definitions in OpenAPI 2.0/3.x format
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
This should go without saying, but the types inside your API specification should be specific in order to be useful. The main way I see this appear is that some specification generators seem to default to "string" for everything, even if something else makes sense. In an analysis of 1154 specifications from OpenAPI directory, I found that 60% of the field types were strings. Many of these were instances that made sense, such as IDs or names, but many were misused types: for example, there was a year value encoded with type "string," and a boolean value with type "string" and enum "true" or "false". Using too-broad types such as strings can make it harder to understand the specification, and decrease the effectiveness of certain tools.
Related posts
-
ApiVault: One-Stop Resource for API Integration
-
Show HN: An open-source OpenAPI package manager – openpm.ai
-
Automatic npm publishing, with GitHub Actions & npm granular tokens
-
APIRank.dev - we crawled and ranked 5651+ public APIs from the internet 🔭
-
What in your opinion is a growing trend? What should people and organisations be paying attention to going forward?