API Keys

Manage your API keys to authenticate your requests and start running tests using the WebPageTest API.

WebPageTest requires an API key to submit any test using the API. If you don't provide an API key when trying to run a test, the API will return an error. Each account receives separate keys for interacting with the API.

Signing Up for the API

To get started with WebPageTest API, you'll need to first create an account and purchase a subscription plan.

If you already have an account, go to My Account on WebPageTest and purchase a subscription plan by clicking on + API Subscription Plan. Once you complete your purchase, you'll be able to generate the API key and start testing using the WPT API.

We currently offer 4 subscription plans (billed monthly or annually) based on the total test runs you wish to run in a month. All our subscription plans offer the same features and capabilities. You can read more about account, tests, and billing or payment questions here.

For Custom Enterprise plans where you want to run more than 20,000 tests per month, please contact us.

Obtaining your keys

Once created, your API keys are always available in your account dashboard, under API Consumers.

Screenshot of the API Consumers section of the account dashboard, showing the name of the key, a link to reveal the key itself, and the dates the key were created and last updated.

To create a new key, select the + New API Key button and enter the a name for the application you'll be using the key for, so you can easily identify which key is used in which context.

Screenshot showing the 'New API Key' button, with a text field under it to enter the application name, along with a save button

For your security, API keys are hidden by default in your dashboard, and can be revealed by selecting the View link.

Currently, we only support one user account to sign in and set up your account to purchase the WebPageTest API. However, you can generate up to 30 keys for multiple use cases and teams, from a single WebPageTest API account. You can generate a new key by selecting the + New API Key button.

We have plans to support adding multiple users and defining roles in the future.

Keeping your keys secret and safe

Your API keys are directly tied to your account and can be used to submit tests, which impact your billing. You should plan to keep them secret and safe, just as you would with any account password. Only share your key with the people who absolutely need access and make sure to keep your keys out of any version control system. We recommend storing them in a password manage or secrets management system.

If a key is compromised, you should delete the key and create a new one.