A padlock sitting on top of a keyboard.

How to Protect Existing GraphQL Endpoints using an API Gateway

You’ve spent months building a GraphQL API. The schema is just right, and your front-end developers are thrilled with it. At first it’s only exposed internally, so you’re not that worried about security, but then as different clients find out that you have this awesome API out there, they want to start using it as well. And oh, the mobile team wants to start taking advantage of this thing, which will introduce clients from all over the world.
As what was initially an internal/hobby project turns into an enterprise API that has a need for enterprise-grade security, you decide to harness the power of an API gateway and Arvata GraphQL Security Proxy to give you the confidence you need to ensure your endpoint isn’t at risk. While the gateway and the proxy work their magic to keep you protected, you get to focus on doing what you do best: developing an awesome API for your clients.

This video uses Layer7 API Management to demonstrate how to protect your endpoints.