JSOPanel Get started
Help Center › Resellers › Creating API tokens

Creating API tokens

Generate scoped tokens so other software can manage your accounts on your behalf.

An API token lets other software, most commonly a billing system or an AI assistant, connect to JSOPanel on your behalf and carry out actions automatically, such as creating a hosting account the moment a customer's order is paid for. A token is scoped to your own reseller account, so it can only ever see and manage your own customers, never anyone else's.

Creating a token

  1. Click MCP & API tokens in the sidebar, under Automation.
  2. Make sure you're on the API tokens tab.
  3. Under Make a token, fill in What is it for, a name that describes what it's for, such as WHMCS integration.
  4. Set Stops working after to a number of days, or leave it at 0 so the token never expires on its own.
  5. Tick a box under What may it change? for each thing the token should be allowed to do, for example Create hosting accounts or Suspend and unsuspend accounts. Leave them all unticked for a token that can only read, which is what most software needs until it starts creating or changing accounts.
  6. Optionally list one address or range per line under Usable from, so the token only works from your billing system's own server. Leave it empty to allow any address.
  7. Click Make the token.

The token's value is shown once, immediately after creation, in a box at the top of the page. Copy it straight away and store it somewhere safe, JSOPanel will not show it to you again.

Tip: give each connected system its own token, rather than reusing one token everywhere. If you ever need to disconnect one system, you can revoke just its token without affecting anything else.

Managing existing tokens

The list at the bottom of the API tokens tab shows every token you've created, what it may change, where it's usable from, and when it was last used. Click Edit on a token to change its permissions or its allowed addresses, or Revoke to stop it working entirely.

Revoking a token

  1. Find the token in the list.
  2. Click Revoke.
  3. Confirm the action.

Once revoked, the token stops working immediately, and any system trying to use it is refused. A revoked token stays in the list, marked as no longer working, until you click Delete to clear it away.

If an AI assistant is using your token

The same tokens can also be used by an AI assistant connected to your account. On the AI assistant permissions tab of the same page, you can choose whether an assistant is asked to confirm first, or simply tells you afterwards, before it deletes an account, deletes a domain, or reads a mailbox's messages.

Connecting Claude specifically

JSOPanel speaks MCP (Model Context Protocol), which Claude supports as a custom connector, in both Claude.ai in a browser and the Claude desktop app. Claude's own menu names can shift over time, but as of this writing:

  1. In Claude, go to Customize → Connectors and click Add custom connector.
  2. Give it a name, and for the server URL enter your server's address followed by /mcp, for example https://yourpanel.example.com/mcp.
  3. For Authentication, choose No sign-in.
  4. Open Request headers. Add one: pick authorization from the list (or Custom header), and for the value enter Bearer followed immediately by your token, for example Bearer jsop_abc123.... Mark it Required.
  5. Click Add, then turn the connector on for a conversation from the + button in the chat box, under Connectors.
Important: Claude sends the header value exactly as typed, it doesn't add "Bearer" for you, so the space between "Bearer" and the token matters.
If you don't see Request headers: this is a newer part of Claude's own interface and isn't available to every account yet. If it's missing, there's currently no way to connect this way, check back later.