Skip to main content
You connect Zorus once at the MSP level. One API token covers every customer its user can see.

​
1. Generate the API token

A Zorus API token acts with the permissions of the portal user you choose for it, and only a System Administrator can generate one. Choose a user with access to the customers Neo should work on: reading endpoints and unblock requests needs read access, and endpoint actions need a user who may run them.
1

Open API Access

Sign in to the Zorus portal as a System Administrator, and open Integrations > API Access.
2

Generate the token

Click Generate API Token, choose the user whose permissions Neo should have, name the token Neo, and generate it.
3

Copy the token

Copy the token. Zorus shows it only once.
Rotating, disabling or deleting the token on the API Access page cuts Neo off at once. Save the new token here when you rotate it.

​
2. Add the token in Neo

1

Open Integrations

In the Neo Dashboard, open Integrations and find the Zorus card, under DNS & Web Filtering.
2

Save the token

Paste the API token and click Save settings. Paste the token alone; Neo adds the Impersonation prefix. Neo checks it against Zorus before saving, so a wrong token is rejected straight away.

​
3. Route unblock request emails to tickets

Zorus emails each unblock request with the subject {Customer Name} Requests to Unblock Domain. To have an agent work them, send those emails to your PSA’s support mailbox, so each one opens a ticket, and route it to the customer’s company. Zorus’s own guide for ConnectWise PSA: Routing Zorus Unblock Requests in ConnectWise Manage.

​
4. Turn Zorus on per agent

Open the agent, go to its Tools & Settings tab, click DNS & Web Filtering, and expand the Zorus block. Pick one of its Presets, or set each area yourself: See Zorus API for what the agent can read and change.