Keys and security
An API key is the whole login for your account's requests. Treat it like a password.
Handling keys
- Keep keys on your server, in an environment variable or a secret store. Never ship one in a browser app, a mobile app or a public repository.
- Create one key per project or server in the dashboard, so you can revoke one without touching the others. An account can have 20 keys.
- A key is shown once, when it is created. We store only a hash and cannot show it again.
- Revoking a key takes effect within 30 seconds at most.
Restrict a key to your IP addresses
In the dashboard you can give each key a list of up to 20 IP addresses. Calls from anywhere else are refused with ip_not_allowed, even with the correct key.
Protect the dashboard login
Turn on two-step sign-in under Settings. After your password the dashboard then asks for a 6-digit code from an authenticator app. You receive ten recovery codes for the case that you lose your phone; each works once. API keys are not affected: your programs keep working as before.
Transport
The API is reachable over HTTPS only. Requests to targets use whatever scheme your URL has: for https:// targets the TLS connection is made by our modem and the target's certificate is verified.
What we store
| Stored for each request | Never stored |
|---|---|
| Time, method, target host, target status or error code | The URL's path and query string |
| Bytes up and down, duration, credits | Request and response headers |
| Exit IP and mobile network | Request and response bodies |
Acceptable use
Do not use the service to attack, overload or break into systems, or for anything illegal where you or the target are. Accounts that do are suspended. Targets in private networks are blocked technically.