Skip to main content
You connect Senteon once at the MSP level. One API key covers every tenant you give it Read on.

Before you start

Senteon’s Public API is not available on trial plans, so your Senteon organization needs a paid subscription.

1. Create the API key

1

Open the API keys

Sign in to the Senteon Command Center at app.senteon.co. Open Settings > Integration > API Keys > Manage API Keys and choose Add New API Key.
2

Give it Read on every tenant

Name it Neo. Turn on Allow All Tenants To Be Read, so Neo can list your tenants and map them to your PSA companies. Under Permissions Scope by Tenant, choose Set All to Read, or set Read on each customer Neo should reach.
3

Copy the Key ID and Key Secret

Click Create Key, and copy the Key ID and the Key Secret. Senteon shows the secret only once. Store it only in Neo.
Senteon gives each key a request budget per minute (60 by default) and counts every call against a monthly quota per key and per organization. Neo uses at most 50 calls a minute. If Neo reports that the quota is used up, raise the key’s request limit in Senteon.

2. Add the key in Neo

1

Open Integrations

In the Neo Dashboard, open Integrations and find the Senteon card, under Vulnerability & Attack Surface.
2

Save the key

Paste the Key ID and the Key Secret into their own fields and click Save settings. Neo checks the key against Senteon before saving, so a wrong key is rejected straight away.
Neo then maps your Senteon tenants to your PSA companies. Check the Organization Mapping tab on the card, and confirm or correct each suggested match. If the tab lists no tenants, the key was created without Allow All Tenants To Be Read: create a new key with it on, and save it here.

3. Turn Senteon on per agent

Open the agent, go to its Tools & Settings tab, click Vulnerability & Attack Surface, and expand the Senteon block. Pick the Read Only preset, or set each area yourself: See Senteon API for what the agent can read.