APIs are ruling the digital transformation efforts and projects. We all talk about APIs. The world is aware about the existence of the APIs. We have API Designers, API Developers and API Architects. APIs are a first class citizen in the Cloud. The Cloud itself cannot be understood without APIs. APIs are creating new business. APIs are products. API Management solutions are part of every CIO agenda. Fintechs, Mobile Virtual Operators, Mobility Applications, Food Delivery solutions, Super market solutions are just a few examples on how APIs are the enablers for doing business on a different way. If we are API consumers, we expect APIs to be designed in such a way that can be understood on a very simple manner, with no effort. We all expect well-designed APIs. If we are API designers and publishers, we better have good principles to create them. But...what happens when we need to design APIs for an event-driven architecture? What is the best option for that an why? Is it really possible to have an specification that can be used to describe events on an API fashion? Is there any value for that? This session is exactly to answer those questions. We will showcase the AsyncAPI initiative and you can apply it to your projects.