Skip to main content
Every request to the Reseller API carries your reseller key in a header:
Note that this is a different header from the one used by the residential usage API, which uses x-api-key. The reseller key is scoped to your reseller account and its data pool.
cURL

​
Keeping your key safe

Your reseller key can spend your data allocation. Treat it like a password: keep it server-side, and never put it in client-side code, URLs, or logs.
Your key is shown once, when it’s issued. There’s no way to read it back later.

​
Rotating your key

If you lose your key — or suspect it’s been exposed — rotate it from your Roundproxies dashboard under Reseller → Rotate key. Rotation is immediate and unforgiving:
  • The old key stops working the moment the new one is issued. There’s no grace period.
  • The new key is shown once, same as the original.
  • Any running integration still sending the old key starts failing with 401 Invalid reseller API key.
Deploy the new key everywhere before you rotate, or expect a gap.
Rotating your key does not affect your sub-users. Their proxy credentials are independent and keep working.

​
Troubleshooting

See Error Handling for the full error reference.