<tenant>.avanan.net).
1. Get the API key
1
Ask Avanan Support for a Smart API key
Open a request with Avanan Support (or Check Point support) for a Smart API key. As an MSP, ask for the MSP API key: one key reaches every client tenant you manage in one region, so you do not need a key per client.
2
Choose the region
An API key works for one region: United States, Europe, Australia, Canada, United Kingdom or India. If your client tenants are in more than one region, Avanan issues a key per region. Neo connects one key, so connect the region most of your clients are in.
3
Keep the secret safe
Avanan Support sends the Application ID and the Client Secret. Treat the Client Secret like a password.
2. Add the key in Neo
1
Open Integrations
In the Neo Dashboard, open Integrations → Avanan, under Security.
2
Save the key
Choose the region, paste the Application ID and the Client Secret, and click Save settings. Neo asks Avanan for a token with them before saving, so a mistyped key, or a key from another region, is rejected straight away.
3. Turn Avanan on per agent
1
Open the agent
In the Neo Dashboard, open the agent and its Integrations tab.
2
Choose an access profile
Under Avanan, choose a profile, or set each permission group by hand.
3
Tell the agent what to do
Add a line to the agent’s instructions, for example: “When a ticket is an allowed list request, add the sender or domain it names to the client’s Avanan allow list and note the entry on the ticket.”
Under every profile, a technician approves creating or licensing a client tenant, every change to your Avanan portal users and child MSPs, and the engine call
POST sectool-exceptions/<engine>, which Avanan’s guide documents both as “create an exception” and as “delete all exceptions”. The Avanan API page lists the permission groups and what Neo never sends.