Creating GraphQL API Keys
As a developer I'm tasked with implementing a custom interface on iOS, Android, or Web to powers up thousands of messages over graphql. But I need a backend system and that's where our fully managed GraphQL API comes into play. Letting you retain control over how your touchpoint is designed while providing a simple plug & play, documented, and ready to scale API. Our stack sits on top of leading cloud technologies on AWS handling global messaging securely in regional data centers whether your customers are located in Europe or the US.
Creating an API key is simple, let's take a look at setting up a test messaging pipeline for a custom live chat experience. From the home screen click on GraphQL. By default a system API key will automatically be generated for you to embed Live Chat or Chatbots onto your website. In this case I'm going to go ahead and Generate a new API key.
Go ahead and give it a friendly name to identify what this GraphQL access token is being used for. If you're embedding on the web specify a domain name without prefixes or localhost for testing on your machine. Each API key has a set of Scopes used to is validate out read and write capability and more details can be found in our documentation. Scopes makes sure that the API key is only going to have a limited subset of capability such as creating chat sessions and sending messages or specifying Auto Reply to allow Chatbots to engage customers. Once you click Generate Token, copy it down as you won't be able to access the secret API key later.