Secure an API by requiring API keys

It's important to protect your API from unauthorized access. One way to do that is with API keys.

When an app makes a request to an API proxy that is configured to verify an API key, the app must supply a valid key. At runtime, the Verify API Key policy checks that the supplied API key:

Is valid
Hasn't been revoked
Matches the API key for the API product that exposes the requested resources

If the key is valid, the request is allowed. If the key is invalid, the request results in an authorization failure.

Create the API proxy

Go to the Apigee UI and sign in.
Select your organization using the drop-down menu in the upper left corner of the UI.
Click Develop > API Proxies to display the API proxies list.
Click Create New.
In the Build a Proxy wizard, select Reverse proxy (most common).

Configure the proxy as follows:

In this field	do this
Proxy Name	Enter: `helloworld_apikey`
Project Base Path	Change to: `/helloapikey` The Project Base Path is part of the URL used to make requests to the API proxy.
Description	Enter: `hello world protected by API key`
Target (Existing API)	Enter: `http://mocktarget.apigee.net` This defines the target URL that Apigee invokes on a request to the API proxy. This target just returns a simple response: `Hello, Guest!`.

Click Next.
On the Common policies page, select API Key. This option automatically adds two policies to your API proxy and creates an API product needed for generating the API key.
Click Next.
On the Summary page, make sure a deployment environment is selected, and click Create and deploy.
Click Edit proxy to display the Overview page for the API proxy.

View the policies

In the API proxy editor, click the Develop tab. You'll see that two policies have been added to the request flow of the API proxy:
- Verify API Key – Checks the API call to make sure a valid API key is present (sent as a query parameter).
- Remove Query Param apikey – An Assign Message policy that removes the API key after it's checked, so that it doesn't get passed around and exposed unnecessarily.
Click the Verify API Key policy icon in the flow view, and look at the policy's XML configuration in the lower code view. The <APIKey> element tells the policy where it should look for the API key when the call is made. By default, it looks for the key as a query parameter called apikey in the HTTP request:
```
<APIKey ref="request.queryparam.apikey" />
```
The name apikey is arbitrary and can be any property that contains the API key.

Try to call the API

In this step, you'll make a successful API call directly to the target service, then you'll make an unsuccessful call to the API proxy to see how it's being protected by the policies.

Success

In a web browser, go to the following address. This is the target service that the API proxy is configured to forward the request to, but you'll hit it directly for now:
```
http://mocktarget.apigee.net
```
You should get this successful response: Hello, Guest!
Failure

Now try to call your API proxy:
```
curl -v -k https://YOUR_ENV_GROUP_HOSTNAME/helloapikey
```
where YOUR ENV_GROUP_HOSTNAME is the environment group hostname. See Find the environment group hostname.

Note: If you have trouble calling the proxy, you may need to add the Host header, as described in Deploy a sample proxy.

Without the Verify API Key policy, this call would give you the same response as the previous call. But in this case, you should get the following error response:
```
{"fault":{"faultstring":"Failed to resolve API Key variable request.queryparam.apikey","detail":{"errorcode":"steps.oauth.v2.FailedToResolveAPIKey"}}}
```
which means, correctly, that you didn't pass a valid API key (as a query parameter).

In the next steps, you'll get the required API key.

Adding an API product

To add an API product using the Apigee UI:

Select Publish > API Products.
Click +Create.

Enter the Product Details for your API product.

Field	Description
Name	Internal name of the API product. Do not specify special characters in the name. Note: You cannot edit the name once the API product is created.
Display name	Display name for the API product. The display name is used in the UI and you can edit it at any time. If not specified, the Name value will be used. This field is auto-filled using the Name value; you can edit or delete its contents. The display name can include special characters.
Description	Description of the API product.
Environment	Environments to which the API product will allow access. For example, `test` or `prod`.
Access	Select Public.
Automatically approve access requests	Enable automatic approval of key requests for this API product from any app.
Quota	Ignore for this tutorial.
Allowed OAuth Scopes	Ignore for this tutorial.

In the Operations section, click ADD AN OPERATION.
In the API Proxy field, select the API proxy you just created.
In the Path field, enter "/". Ignore the other fields.
Click Save to save the Operation.
Click Save to save the API product.

Add a developer and app to your organization

Next, we're going to simulate the workflow of a developer signing up to use your APIs. A developer will have one or more apps that call your APIs, and each app gets a unique API key. This gives you, the API provider, more granular control over access to your APIs and more granular reporting on API traffic by app.

Create a developer

To create a developer:

Select Publish > Developers in the menu.
Note: If you are still in the Develop screen, click on the "<" by DEVELOP to display the menu and select Publish > Developers
Click + Developer.

Enter the following in the New Developer window:

In this field	enter
First Name	`Keyser`
Last Name	`Soze`
Username	`keyser`
Email	`keyser@example.com`

Click Create.

Register an app

To register a developer app:

Select Publish > Apps.
Click + App.

Enter the following in the New Developer App window:

In this field	do this
Name and Display Name	Enter: `keyser_app`
Developer	Select: `Keyser Soze (keyser@example.com)`
Callback URL and Notes	Leave blank

In the Credentials section, select Never. The credentials for this app will never expire.
Click Add product.
Select the product you just created.
Click Create.

Get the API key

To get the API key:

On the Apps page (Publish > Apps), click keyser_app.
On the keyser_app page, click Show next to Key in the Credentials section. Notice that the key is associated with the product you created.
Select and copy the key. You'll use it in the next step.

Call the API with a key

Now that you have an API key, you can use it to call the API proxy. Paste the API key as shown, as a query parameter. Make sure there are no extra spaces in the query parameter.

curl -v -k https://YOUR_ENV_GROUP_HOSTNAME/helloapikey?apikey=your_api_key

Now when you call the API proxy, you should get this response: Hello, Guest!

Congratulations! You've created an API proxy and protected it by requiring that a valid API key be included in the call.

Note that in general it's not good practice to pass an API key as a query parameter. You should consider passing it in the HTTP header instead.

Best practice: Passing the key in the HTTP header

In this step, you will modify the proxy to look for the API key in a header called x-apikey.

Edit the API proxy. Select Develop > API Proxies > helloworld_apikey, and go to the Develop view.
Select the Verify API Key policy, and modify the policy XML to tell the policy to look in the header rather than in the queryparam:
```
<APIKey ref="request.header.x-apikey"/>
```
Save the API proxy and use Deploy to deploy it.
Make the following API call using cURL to pass the API key as a header called x-apikey. Don't forget to substitute your organization name.
```
curl -v -H "x-apikey: {api_key_goes_here}" http://YOUR_ENV_GROUP_HOSTNAME/helloapikey
```

Note that to fully complete the change, you'd also need to configure the Assign Message policy to remove the header instead of the query parameter. For example:

<Remove>
  <Headers>
      <Header name="x-apikey"/>
  </Headers>
</Remove>