canonical: https://jentic.com/apis/tenable.com/mssp-portal

# Tenable MSSP Portal

The Tenable Managed Security Service Provider (MSSP) Portal API provides a secure and accessible way for MSSP administrators to manage and maintain multiple customer instances of Tenable products. Endpoints in the Tenable MSSP Portal API enables customers to view and manage your MSSP customer accounts. For more information about the Tenable MSSP Portal, see the [Tenable MSSP Portal User Guide](htt. The API exposes 34 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create evaluation account v1, create evaluation account v2. Covers 34 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for e-commerce only.

## Capabilities

- Create evaluation account v1
- List child accounts
- Get child account details
- Query and filter MSSP Portal records by parameters
- Monitor MSSP Portal operational status and events

## Use cases

### E-Commerce Operations

Use the MSSP Portal to perform e commerce operations programmatically. The API provides 34 endpoints covering core functionality including create evaluation account v1, create evaluation account v2, create quote.

Example prompt: Call POST /mssp/accounts/eval to create evaluation account v1

### Automated Accounts Management

Automate accounts operations by combining multiple MSSP Portal endpoints. Agents can create evaluation account v2 and then create quote in a single workflow.

Example prompt: Call POST /mssp/accounts/v2/eval to create evaluation account v2, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call MSSP Portal endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'create evaluation account v1', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /mssp/accounts/eval | Create evaluation account v1 |
| POST | /mssp/accounts/v2/eval | Create evaluation account v2 |
| POST | /mssp/accounts/quote | Create quote |
| GET | /mssp/accounts | List child accounts |
| GET | /mssp/accounts/{account_uuid} | Get child account details |
| GET | /mssp/accounts/{account_uuid}/domains | List domains |
| POST | /mssp/accountGroup | Create account group |
| GET | /mssp/accountGroup | List account groups |

## Key resources

- **Accounts** — The Tenable Managed Security Service Provider (MSSP) Portal API provides a secure and accessible way
- **Account Groups** — The Tenable Managed Security Service Provider (MSSP) Portal API provides a secure and accessible way
- **Child Containers** — The Tenable Managed Security Service Provider (MSSP) Portal API provides a secure and accessible way
- **Dashboards** — The Tenable Managed Security Service Provider (MSSP) Portal API provides a secure and accessible way
- **Domains** — The Tenable Managed Security Service Provider (MSSP) Portal API provides a secure and accessible way

## Why Jentic

- **Setup:** Wiring the Tenable MSSP Portal by hand means learning its X-ApiKeys header auth (accessKey plus secretKey) against the cloud.tenable.com host and handling account and account-group calls yourself. Through Jentic you install once, import MSSP Portal from the API Directory, store the key pair once, and your agent calls it.
- **Permission scoping:** MSSP Portal puts the account id in the URL path (/mssp/accounts/{account_uuid}), so a rule can pin your agent to one managed account: it can read that account and its domains and nothing else. You choose the operations it may call, so creating evaluation accounts or quotes is not included unless you add it.
- **Credential handling:** Your MSSP Portal access key and secret key are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list managed accounts' or 'get an account's domains', and Jentic returns the matching MSSP Portal operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Shopify** — Alternative e commerce API
- **Stripe** — Alternative e commerce API

## FAQ

### What authentication does the MSSP Portal use?

The MSSP Portal uses an API key passed in the `X-ApiKeys` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I create evaluation account v1 with the MSSP Portal?

Yes. Use the POST /mssp/accounts/eval endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the MSSP Portal?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I create evaluation account v1 through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create evaluation account v1'. Jentic returns the matching MSSP Portal operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the MSSP Portal have?

The MSSP Portal exposes 34 endpoints covering accounts, account groups, child containers operations.

### Can I limit what my agent is allowed to do with the MSSP Portal API?

Yes. Because you run Jentic One yourself, your own rules decide which MSSP Portal operations and credentials the agent may use. Since the account id sits in the URL path (/mssp/accounts/{account_uuid}), you can pin the agent to a single managed account so it only reads that account and its domains through GET /mssp/accounts/{account_uuid} and the list-domains call. You choose the operations it may reach, so creating evaluation accounts or quotes stays off limits unless you explicitly allow it.