The community space for @Openapi — APIs, open source, ideas, projects and conversations.
Our repositories are where the code lives. This is where the people are.
Every Openapi SDK, tool and integration has its own repository, its own issues and its own release notes. That works well for bugs and pull requests, and badly for everything else: the questions that do not have a single right answer, the thing you built over a weekend, the integration that should exist and does not, the opinion you have about rate limits that nobody asked for.
All of that belongs here. You do not need to be a customer, a contributor, or an expert. If you build things that talk to APIs, you are in the right place.
No introduction required. Pick a thread that looks interesting and say what you think — a one-line answer is a real answer, and an upvote is a real contribution.
| Category | For |
|---|---|
| 💡 Ideas | What should exist and does not yet. Integrations, tools, SDKs, recipes. |
| 💬 General | API design, tooling, workflows, and opinions about both. |
| 🙌 Show and tell | Something you built. Small is welcome — small is better, actually. |
| 🧠 Open Source AI | Agents, MCP servers, evals, and everything that happens when an LLM meets a real API. |
| 🙏 Q&A | Questions with an answer. Ask, and mark what solved it. |
| 🗳 Polls | Quick calls where a vote says more than a comment. |
| 💓 Openapi Pulse | The editions of the Pulse — see below. |
| 📣 Announcements | Releases and news from the Openapi team. |
The card at the top of this page is the Openapi Pulse — a regular edition of what is moving in the ecosystem: an API worth a look, a developer and a contributor from the community, and the discussion worth joining this time around.
It runs on a rotation, so the people it features change on their own. Two ways to end up on it:
- be a member of the Openapi organization
- add yourself to the contributors registry — it is a single pull request, and it is what puts you in the rotation
Every edition is archived in the Openapi Pulse category.
- Answer a thread. One line is enough.
- Show what you built. Even the forty-line script nobody asked for.
- Ask for an integration. If several people ask for the same one, that is a roadmap.
- Contribute to a repository. Every Openapi project takes pull requests.
- Bring a question from your own work. The ones from real projects are the good ones.
Be decent to each other, assume the other person is trying to help, and keep it technical. That is the whole moderation policy.
Maintainer: Francesco Bianco
Owner: Openapi S.p.A.
Made by developers, for developers ⚡