About

Maintainers #︎

AsyncAPI is actively maintained by:

So far, we have had many contributors and we are thankful for their time and help.

Contributors #︎

We do our best to recognize every contribution to the project. We do it individually in every repository from AsyncAPI GitHub organization. There should always be a Contributors section in the readme, like this one. We use All Contributors specification to handle recognitions.

We apologize in advance if we failed in recognizing your work. Feel free to contact us on slack and we will fix it immediately, or just talk to All Contributors bot.

Companies support #︎

This is the list of companies that either provide a significant financial support or delegate their employees to support AsyncAPI with maintainance:

Would you like to get on the list and support us financially? Check out the sponsoring options.

Would you like to help us with the maintainance? Contact us on slack.

History #︎

This project started at Hitch (a.k.a. API Changelog). We are in love with API machine-readable documentation formats (OpenAPI, RAML, etc.) and always encouraged our customers to use a machine-readable definition for their APIs because it allows them to get extra benefits. From documentation and code generation to setup their own API Assistant.

Internally, we used a message-driven microservices architecture and we couldn’t have all those tools that we have with the HTTP APIs. All those things you get because you have your API defined with a machine-readable documentation format. And, on top of that, we noticed that some of our customers were creating IoT APIs over MQTT and they couldn’t get all the benefits from Hitch because the existing specifications don’t support message-driven APIs.

It was time to come up with something good enough for everyone instead of having every company doing its own battle. We can learn a lot together if we join forces, so we decided to create AsyncAPI!