Authentication

Reseller endpoints accept two kinds of credentials:

Credential	Header	Use it for
Reseller key	`x-reseller-key: rsl_...`	Servers, scripts and other integrations
Dashboard token	`Authorization: Bearer <jwt>`	Calls made as the logged-in user of the reseller account

If you send both, the reseller key is used.

cURL

curl https://api.roundproxies.com/reseller/account \
  -H "x-reseller-key: rsl_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"

x-reseller-key is not the same header as the residential usage API, which uses x-api-key. The reseller key only works for your reseller account and its pool.

The key under Dashboard → API is not a reseller key. That key starts with rp_ and only works on the residential usage API with x-api-key. Reseller keys start with rsl_ and are issued separately once reseller access is turned on. Sending an rp_ key to any /reseller/* endpoint returns 401 Invalid reseller API key, whichever header you use.

Since the dashboard token also works, a logged-in user with reseller access doesn’t need an API key. The key is for integrations that run without someone logged in.

Keeping Your Key Safe

Your reseller key can spend your data and your proxy capacity. Treat it like a password: keep it on your server and never put it in client-side code, URLs or logs.

Your key is shown once, when it is created. We only store a hash of it, so nobody can look it up later, including support.

Checking Your Access

GET /reseller/self

Use your dashboard token here, not the reseller key. It tells you whether the logged-in user has reseller access.

cURL

curl https://api.roundproxies.com/reseller/self \
  -H "Authorization: Bearer $JWT"

Response

{
  "hasResellerAccess": true,
  "isActive": true,
  "account": { "...": "..." }
}

Rotating Your Key

POST /reseller/self/rotate-key

This also uses your dashboard token, so it works even if you lost the key. The new key is returned once, in the response.

cURL

curl -X POST https://api.roundproxies.com/reseller/self/rotate-key \
  -H "Authorization: Bearer $JWT"

Status	Meaning
`404`	This user has no reseller access
`403`	The reseller account is suspended

You can also rotate the key in your dashboard under Reseller → Rotate key. Rotation takes effect immediately:

The old key stops working as soon as the new one is created. There is no grace period.
The new key is shown once, like the first one.
Anything still using the old key starts failing with 401 Invalid reseller API key.

Roll out the new key everywhere right after rotating, or expect a short outage.

Rotating your key doesn’t affect your sub-users or proxy allocations. Their credentials keep working.

Suspension

A suspended reseller account (isActive: false) gets 401 on every reseller endpoint. Existing sub-users keep working until their data runs out, so your customers aren’t cut off right away.

Troubleshooting

Problem	Likely cause	Fix
`401 Invalid reseller API key`	Wrong key, or the key was rotated.	Compare the key you use with `apiKeyPrefix` from `GET /reseller/account`. If it’s lost, rotate and roll out the new one.
`401 Invalid reseller API key` with a key starting with `rp_`	That is your residential API key from Dashboard → API, not a reseller key.	Call `GET /reseller/self` with your dashboard token. If `hasResellerAccess` is `false`, request access from team@roundproxies.com. If it’s `true`, rotate to get your `rsl_` key.
`401 Reseller account is suspended`	Your reseller account is on hold.	Contact support. Existing sub-users keep working until their data runs out.
`404` on `/reseller/self`	The logged-in user has no reseller access.	Request access from team@roundproxies.com.
Worked yesterday, fails today	Someone rotated the key.	Rotate again with `POST /reseller/self/rotate-key` or in the dashboard, and roll out the new key.

See Error Handling for all errors.

Getting Started

Residential Proxies

ISP Proxies

Datacenter Proxies

Reseller

Keeping Your Key Safe

Checking Your Access

GET /reseller/self

Rotating Your Key

POST /reseller/self/rotate-key

Suspension

Troubleshooting