Tenable Access Control (Users) API

The Access Control (Users) API from Tenable — 10 operation(s) for access control (users).

Business capability
Identity & Access Management BC-620.20

Operations 15

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

POST /users Create a user account · Create user #
Ask an LLM
“How do I add a new person as a user with a username and password?”
“What permission level can I give a brand-new user when I create them?”
Tell an agent
Create a new user {username} with password {password}.
Create user {username} for {name} ({email}) with password {password} and permissions {permissions}.
GET /users List users in the workspace · List users #
Ask an LLM
“Who has a user account in my Tenable Vulnerability Management instance?”
“Can I see each user's role alongside the user list?”
Tell an agent
List every user account in the workspace.
List all users and include their roles (withRoles={with_roles}).
GET /users/{user_id} Get a user's account details · Get user details #
Ask an LLM
“What account details are stored for one specific user?”
“Can I look up a single user's name, email and permissions by their ID?”
Tell an agent
Show me the account details for user {user_id}.
Look up user {user_id} and tell me their email and permission level.
PUT /users/{user_id} Update a user's profile and permissions · Update user #
Ask an LLM
“How do I change an existing user's display name or email address?”
“Can I change a user's permission level after the account exists?”
Tell an agent
Change the email of user {user_id} to {email}.
Update user {user_id}: set name to {name} and permissions to {permissions}.
DELETE /users/{user_id} Delete a user account · Delete user #
Ask an LLM
“How do I permanently remove a user from the workspace?”
“When I delete a user, can their scans and objects be handed over to someone else?”
Tell an agent destructive · confirm first
Delete user {user_id}.
Delete user {user_id} and transfer their objects to user {successor_user_uuid}.
GET /access-control/v1/users/{user_uuid}/roles Get the role assigned to a user · Get user role #
Ask an LLM
“Which role is currently assigned to a given user?”
“Is this user on a standard role or a custom role?”
Tell an agent
Tell me which role user {user_uuid} has.
Get the assigned role for user {user_uuid}.
PUT /access-control/v1/users/{user_uuid}/roles Change a user's role · Change user role #
Ask an LLM
“How do I move a user onto a different custom role?”
“Can I reassign someone's role using the role UUID?”
Tell an agent
Assign role {role_uuids} to user {user_uuid}.
Switch user {user_uuid} over to the roles {role_uuids}.
PUT /users/{user_uuid}/chpasswd Reset a user's password · Change password #
Ask an LLM
“How do I reset a locked-out user's password?”
“Can I set a temporary password that forces the user to change it at next login?”
Tell an agent
Reset the password for user {user_uuid} to {password}.
Give user {user_uuid} the temporary password {password} (temporary={temporary}).
PUT /users/{user_id}/enabled Enable or disable a user account · Enable or disable user account #
Ask an LLM
“How do I temporarily disable a user without deleting them?”
“Can I re-enable an account I switched off earlier?”
Tell an agent
Disable the account of user {user_id} (enabled={enabled}).
Turn user account {user_id} back on.
GET /users/{user_id}/authorizations Get a user's sign-in authorizations · Get user authorizations #
Ask an LLM
“Which sign-in methods (password, SAML SSO, API keys) is a user allowed to use?”
“Is API access permitted for this particular user?”
Tell an agent
Show which access methods user {user_id} is authorized for.
Check whether user {user_id} can sign in with SAML or use the API.
PUT /users/{user_id}/authorizations Grant or revoke a user's access methods · Update user authorizations #
Ask an LLM
“How do I block a user from using the API but keep SSO login?”
“Can I require a user to enroll in multi-factor authentication?”
Tell an agent
For user {user_id} set API access {api_permitted}, password login {password_permitted} and SAML {saml_permitted}.
Require MFA enrollment ({mfa}) for user {user_id} with API {api_permitted}, password {password_permitted}, SAML {saml_permitted}.
PUT /users/{user_id}/keys Generate new API keys for a user · Generate API keys #
Ask an LLM
“How do I issue a fresh access key and secret key for a user?”
“Can an administrator generate API keys on behalf of another user?”
Tell an agent
Generate new API keys for user {user_id}.
Rotate the API access and secret keys of user {user_id}.
POST /users/{user_id}/two-factor/send-verification Text a two-factor verification code · Send verification code #
Ask an LLM
“How do I start setting up SMS two-factor for a user?”
“What phone number format does the two-factor verification code need?”
Tell an agent
Send a two-factor verification code to {sms_phone} for user {user_id}.
Start 2FA setup for user {user_id} by texting a code to {sms_phone}.
POST /users/{user_id}/two-factor/verify-code Confirm a two-factor verification code · Validate verification code #
Ask an LLM
“How do I confirm the SMS code a user received so their two-factor is switched on?”
“What happens after the verification code is validated successfully?”
Tell an agent
Verify code {verification_code} for user {user_id} to finish enabling 2FA.
Validate the 2FA code {verification_code} that user {user_id} received by text.
PUT /users/{user_id}/two-factor Configure a user's two-factor settings · Configure two-factor authentication #
Ask an LLM
“Can I turn off SMS two-factor for a user or enable backup email codes?”
“Which phone number is used once two-factor settings are saved?”
Tell an agent
Set 2FA for user {user_id}: SMS {sms_enabled} to {sms_phone}, backup email {email_enabled}.
Disable SMS two-factor ({sms_enabled}) and email backup ({email_enabled}) for user {user_id}, phone {sms_phone}.

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/tenable:tenable-access-control-users-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

tenable-access-control-users-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Tenable Platform & Settings Access Control (Users) API
  version: 1.0.0
servers:
- url: https://cloud.tenable.com
tags:


# --- truncated at 32 KB (73 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/tenable/refs/heads/main/openapi/tenable-access-control-users-api-openapi.yml