Reseller API authentication

The Reseller API uses a short-lived bearer token. You trade your reseller email and password for a token, then send that token on every other request.

Base URL: https://dashboard.residential.rayobyte.com/

1. Get a token.

   curl -X POST https://dashboard.residential.rayobyte.com/api/reseller/login \
     -H "Content-Type: application/json" \
     -d '{"email":"you@example.com","password":"YOUR_PASSWORD"}'

2. Send it on every other request.

   curl https://dashboard.residential.rayobyte.com/api/reseller/info \
     -H "Authorization: Bearer YOUR_TOKEN"

Token lifetime

Tokens are valid for three hours. After that, requests fail and you log in again for a new one.

Tip

Do not fetch a fresh token per request. Cache it, and re-authenticate when a call comes back unauthorised or when your cached token is close to three hours old.

Query-parameter authentication

The API also accepts a token query parameter as an alternative to the Authorization header. Prefer the header — query strings end up in server logs, browser history and proxy access logs.

Keep your password out of your code

The login call takes your actual reseller account password. Read it from an environment variable or a secret store, never from a committed file.

curl -X POST https://dashboard.residential.rayobyte.com/api/reseller/login \
  -H "Content-Type: application/json" \
  -d "{\"email\":\"$RESELLER_EMAIL\",\"password\":\"$RESELLER_PASSWORD\"}"

Next steps

• Reseller API reference — every endpoint, generated from the spec