HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
OAI
OpenAPI-Specification
Markdown2014–2026
OAI / OpenAPI-Specification

OpenAPI-Specification

The OpenAPI Specification Repository

Web DevelopmentLearning & Reference
Explore on GitHubRead Hacker News discussions
35Distinct people
40Mentions
1Explicit recommenders
31.3KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

The OpenAPI Specification Repository

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

Yep. OpenAPI spec is not rich enough to represent relations like this so its rubbish for FE dev to use to generate models/api client. In general, the tooling/spec has thousands…

adamscybot used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 7:02:50 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year40 dated mentions

Observed mentions: 2014-03-21 01:41:57 UTC to 2026-07-05 14:59:36 UTC.

02462014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments20142015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 6 mentions; 2 submissions, 4 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 6 mentions; 2 submissions, 4 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC413
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC514
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC505
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC624
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC312
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC624
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC514
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC202
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC110
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC101
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC110

What Hacker News says

3 sources
wing328hk·Sep 27, 2019Submission

OpenAPI Generator's Kotlin client generator now supports multiplatform

We've added multiplatform (https://kotlinlang.org/docs/reference/multiplatform.html) support to the Kotlin client generator in the OpenAPI Generator (https://github.com/OpenAPITools/openapi-generator) project. To generate a Kotlin API client with multiplatform support given an OpenAPI/Swagger specification file (https://github.com/OAI/OpenAPI-Specification), please follow 3 simple steps below: 1. Download the Java JAR (https://oss.sonatype.org/content/repositories/snapshots/org/openapitools/openapi-g…) 2. Rename the JAR as "openapi-generator-cli.jar" 3. Run the following command to generate a Nim API client for the Petstore API (https://raw.githubusercontent.com/OpenAPITools/openapi-generator/master/modules/op…):
Read the rest
Mac/Linux: $ java -jar openapi-generator-cli.jar generate -g kotlin -i https://raw.githubusercontent.com/OpenAPITools/openapi-generator/master/modules/op… --library multiplatform -o /var/tmp/kotlin/ Windows: $ java -jar openapi-generator-cli.jar generate -g kotlin -i https://raw.githubusercontent.com/OpenAPITools/openapi-generator/master/modules/op… --library multiplatform -o C:\tmp\kotlin If you've any feedback or question, please let us know via https://github.com/OpenAPITools/openapi-generator/issues/new Thanks for the enhancement by Andrew Emery (https://github.com/andrewemery) Ref: https://github.com/OpenAPITools/openapi-generator/pull/3900
1 points · Open discussion
acemarke·Apr 14, 2019
Some searching turns up some articles on incompatibilities between OpenAPI and JSON Schema [0] [1], and it's not immediately clear if they fit together well at this point. We've got some JSON Schema APIs in our services already and are using libs like the Python `json-schema` package to do validation with those. I also briefly experimented with Quicktype [2] to generate some TS types as a proof-of-concept. We're getting ready to do a pretty big rework of a lot of our services, and I'm interested in any info folks can provide on pros and cons of using OpenAPI vs JSON Schema for API definitions, and tooling around request validation and TS interface / client generation. [0] https://philsturgeon.uk/api/2018/04/13/openapi-and-json-sche... [1] https://github.com/OAI/OpenAPI-Specification/issues/1532 [2] https://quicktype.io/typescript/
In Using JSON Schema to Document, Test, and Debug APIs
sandreas·Feb 6, 2019
My advice is: Use standards and don't reinvent the wheel. There are plenty of them... https://jsonapi.org/ https://github.com/OAI/OpenAPI-Specification http://json-schema.org/ https://graphql.org/learn/ ... And for authentication and authorisation use oauth: https://oauth.net/2/ and prevent states and cookies (!) - use tokens and headers instead. There is no "BEST" option in my opinion, but https://api-platform.com/ is a good place to start for getting things done... and perhaps search for HATEOAS libs in the programming language of your choice.
In Ask HN: How do you prefer to structure web APIs?

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.