1. Create an API key
- Log in to the dashboard.
- Go to Settings → API keys.
- Click Generate new API key, give it a name, and pick its scopes. For this walkthrough you need at least
proxy:packages:read. - Optionally restrict the key to specific packages — a restricted key can only see and act on those packages.
- Copy the secret. It starts with
s_live_and is shown only once — store it somewhere secure right away.
2. Verify the key
CallGET /v1/api-keys/me — it needs no scope and echoes back what the key can do:
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
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 returneduri is a standard proxy URL — pass it to any HTTP client:
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.