Connect handles API authentication using an API Key. A Connect representative will provide you with the key during your setup process. You should treat the key securely.

Note: If you have previously been set up to to use the Apigee API endpoints, that API key is not valid for Connect or the new Legacy endpoints, and you will still need to go through the setup process with a Connect representative.

API Key Flow

When making a call into either the Legacy or Connect APIs, you will need to pass in your API Key using the x-api-key header, like the following request:

curl --location --request GET '' \ 
--header 'x-api-key: <your_api_key>'

If your key is invalid or sent incorrectly, you will recieve an unauthenticated error.