Skip to main content
This guide takes you from zero to a working integration: you’ll create an API key, verify it works, list your proxy packages, and generate a connection string you can plug straight into your proxy client.

1. Create an API key

  1. Log in to the dashboard.
  2. Go to Settings → API keys.
  3. Click Generate new API key, give it a name, and pick its scopes. For this walkthrough you need at least proxy:packages:read.
  4. Optionally restrict the key to specific packages — a restricted key can only see and act on those packages.
  5. Copy the secret. It starts with s_live_ and is shown only once — store it somewhere secure right away.
Treat the secret like a password. Don’t commit it to source control or embed it in client-side code. If a key leaks, revoke it and create a new one.

2. Verify the key

Call GET /v1/api-keys/me — it needs no scope and echoes back what the key can do:
If you get 401 {"detail": "Invalid API key"} instead, check that the header is exactly Authorization: Bearer <secret> and that the key hasn’t been revoked.

3. List your packages

Grab the id of the package you want to use — you’ll need it in the next step.

4. Generate a connection string

The connection-string endpoint builds proxy credentials for you, with targeting rules already encoded — no need to construct the username format by hand:

5. Use it

The returned uri is a standard proxy URL — pass it to any HTTP client:
You’re routed through a US IP. From here you can add sessions, rotation, and finer targeting (region, city, ISP, ASN, ZIP) via the same endpoint’s query parameters.

Next steps

Get connection strings

All targeting, session, and rotation parameters.

Authentication & scopes

What each scope unlocks, and how to manage keys programmatically.

Usage analytics

Pull traffic and credit usage into your own reporting.

Rate limits

Stay under the limits and handle 429s gracefully.