Skip to main content
Single sign-on (SSO) lets you redirect your customers directly into their portal session from your billing system or control panel — no password required.

How it works

  1. Your system calls POST /api/v1/sub-clients/{id}/sso-token with your API token
  2. PanelDNS returns a one-time login_url
  3. You redirect the customer’s browser to that URL
  4. PanelDNS validates the token, creates a session, and lands the customer on their zones page
The token is valid for 60 seconds and single-use — once clicked, it cannot be reused.

WHMCS example

Response

Security notes

  • SSO tokens are signed JWTs with a 5-minute expiry — they cannot be forged without your signing key
  • Each token is single-use — reuse returns 401 Unauthenticated
  • The token is bound to the specific sub-client — it cannot be used to access another sub-client’s portal
  • Tokens are transmitted in the URL query string; use HTTPS in production (enforced by default)
  • Generating an SSO token for a suspended sub-client returns 422 — suspended accounts cannot log in

Custom portal domain

If you have a custom domain configured (e.g. dns.acme-hosting.com), the login_url in the response uses that domain automatically — no extra configuration needed.