Systems | Development | Analytics | API | Testing

Why do APIs require authentication in the first place? Users don't always need keys for read-only APIs. However, most commercial APIs require permission via API keys or other ways. Users might make an unlimited number of API calls without needing to register if your API had no security. Allowing limitless requests would make it impossible to develop a business structure for your API. Furthermore, without authentication, it would be difficult to link requests to individual user data.

Event hooks are a brand new feature we launched with Kong Gateway 2.5 that allows you to get notifications when certain events happen on your Kong Gateway deployment. If you want to keep an eye out for when your system creates new administrators or adds new plugins to a latency-sensitive route, this is the feature for you! Event hooks is a Kong Gateway Enterprise feature. Interested in learning more? Contact our sales team.

As more and more companies move to a multi-cloud strategy and increase usage of a cloud native infrastructure, API providers are under a lot of pressure to deliver APIs at scale in multi-cloud environments. At the same time, APIs should follow each company’s security requirements and best practices, no matter the cloud platform. These reasons explain why many providers have such complex API authorization requirements.

Just under one year ago, we launched version 1.0 of our Kong Ingress Controller (KIC). That was a huge milestone for us here at Kong, and we know it was for you – Kong Nation – as well. Since then, with the help of our community, we’ve merged over 300 new features and bug fixes and have started to enter a new era of KIC: version 2.0. Prior to releasing KIC 2.0, we want to make sure to incorporate community and customer feedback, so we are announcing the KIC 2.0 Beta.