How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Tenable OT Connectors API

The OT Connectors API from Tenable — 4 operation(s) for ot connectors.

Tenable OT Connectors API is one of 107 APIs that Tenable publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include OT Connectors. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 6 operations across 4 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://cloud.tenable.com.

6 operations 4 paths 6 schemas 1 DELETE2 GET2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://cloud.tenable.com
Authentication
API Key, API Key, API Key, API Key, API Key, API Key, API Key, API Key, API Key, API Key, API Key, API Key, API Key, API Key, API Key, API Key, API Key, API Key, API Key, API Key, API Key, API Key, API Key, API Key, API Key, API Key, API Key, API Key, API Key
Resource Areas
1

Authentication & Security 29

Tenable OT Connectors API declares 29 security schemes for authenticating requests. An API key is passed in the header as X-ApiKeys (Access_Control_API_cloud). An API key is passed in the header as X-ApiKeys (Access_Control_Groups_cloud). An API key is passed in the header as X-ApiKeys (Access_Control_Permissions_cloud). An API key is passed in the header as X-ApiKeys (Access_Control_Roles_cloud). An API key is passed in the header as X-ApiKeys (Access_Control_Users_cloud). An API key is passed in the header as X-ApiKeys (access-groups_cloud). An API key is passed in the header as X-ApiKeys (access-groups_v2_cloud). An API key is passed in the header as X-ApiKeys (activity-log_cloud). An API key is passed in the header as X-ApiKeys (agents_cloud). An API key is passed in the header as X-ApiKeys (Agent_Config_cloud). An API key is passed in the header as X-ApiKeys (agent-exclusions_cloud). An API key is passed in the header as X-ApiKeys (agent-groups_cloud). An API key is passed in the header as X-ApiKeys (agent-bulk-operations_cloud). An API key is passed in the header as X-ApiKeys (Cloud_Connectors_cloud). An API key is passed in the header as X-ApiKeys (credentials_cloud). An API key is passed in the header as X-ApiKeys (exclusions_cloud). An API key is passed in the header as X-ApiKeys (networks_cloud). An API key is passed in the header as X-ApiKeys (OT_Connectors_cloud). An API key is passed in the header as X-ApiKeys (permissions_cloud). An API key is passed in the header as X-ApiKeys (Profiles_cloud). An API key is passed in the header as X-ApiKeys (recast-rules_cloud). An API key is passed in the header as X-ApiKeys (Scanners_cloud). An API key is passed in the header as X-ApiKeys (Scanner_Config_cloud). An API key is passed in the header as X-ApiKeys (Scanner_Groups_cloud). An API key is passed in the header as X-ApiKeys (Scanner_Profiles_cloud). An API key is passed in the header as X-ApiKeys (Scanner_Tasks_cloud). An API key is passed in the header as X-ApiKeys (server_cloud). An API key is passed in the header as X-ApiKeys (tags_cloud). An API key is passed in the header as X-ApiKeys (target-groups_cloud).

  • Access_Control_API_cloud — Format - accessKey=ACCESSKEY;secretKey=SECRETKEY
  • Access_Control_Groups_cloud — Format - accessKey=ACCESSKEY;secretKey=SECRETKEY
  • Access_Control_Permissions_cloud — Format - accessKey=ACCESSKEY;secretKey=SECRETKEY
  • Access_Control_Roles_cloud — Format - accessKey=ACCESSKEY;secretKey=SECRETKEY
  • Access_Control_Users_cloud — Format - accessKey=ACCESSKEY;secretKey=SECRETKEY
  • access-groups_cloud — Format - accessKey=ACCESSKEY;secretKey=SECRETKEY
  • access-groups_v2_cloud — Format - accessKey=ACCESSKEY;secretKey=SECRETKEY
  • activity-log_cloud — Format - accessKey=ACCESSKEY;secretKey=SECRETKEY
  • agents_cloud — Format - accessKey=ACCESSKEY;secretKey=SECRETKEY
  • Agent_Config_cloud — Format - accessKey=ACCESSKEY;secretKey=SECRETKEY
  • agent-exclusions_cloud — Format - accessKey=ACCESSKEY;secretKey=SECRETKEY
  • agent-groups_cloud — Format - accessKey=ACCESSKEY;secretKey=SECRETKEY
  • agent-bulk-operations_cloud — Format - accessKey=ACCESSKEY;secretKey=SECRETKEY
  • Cloud_Connectors_cloud — Format - accessKey=ACCESSKEY;secretKey=SECRETKEY
  • credentials_cloud — Format - accessKey=ACCESSKEY;secretKey=SECRETKEY
  • exclusions_cloud — Format - accessKey=ACCESSKEY;secretKey=SECRETKEY
  • networks_cloud — Format - accessKey=ACCESSKEY;secretKey=SECRETKEY
  • OT_Connectors_cloud — Format - accessKey=ACCESSKEY;secretKey=SECRETKEY
  • permissions_cloud — Format - accessKey=ACCESSKEY;secretKey=SECRETKEY
  • Profiles_cloud — Format - accessKey=ACCESSKEY;secretKey=SECRETKEY
  • recast-rules_cloud — Format - accessKey=ACCESSKEY;secretKey=SECRETKEY
  • Scanners_cloud — Format - accessKey=ACCESSKEY;secretKey=SECRETKEY
  • Scanner_Config_cloud — Format - accessKey=ACCESSKEY;secretKey=SECRETKEY
  • Scanner_Groups_cloud — Format - accessKey=ACCESSKEY;secretKey=SECRETKEY
  • Scanner_Profiles_cloud — Format - accessKey=ACCESSKEY;secretKey=SECRETKEY
  • Scanner_Tasks_cloud — Format - accessKey=ACCESSKEY;secretKey=SECRETKEY
  • server_cloud — Format - accessKey=ACCESSKEY;secretKey=SECRETKEY
  • tags_cloud — Format - accessKey=ACCESSKEY;secretKey=SECRETKEY
  • target-groups_cloud — Format - accessKey=ACCESSKEY;secretKey=SECRETKEY

Paths & Operations 6

Across 4 paths, the API surfaces 6 operations — 1 DELETE, 2 GET, 2 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

OT Connectors 6
POST
/sensors
Create OT connector
sensors-ot-create 2 params body → 200400401429500
GET
/sensors/{type}
List OT connectors
sensors-ot-list 6 params → 200400401403429500
GET
/sensors/{type}/{id}
Get OT connector details
sensors-ot-details 2 params → 200400401403404429500
PUT
/sensors/{type}/{id}
Update OT connector
sensors-ot-update 2 params body → 200400401403404429500
DELETE
/sensors/{type}/{id}
Delete OT connector
sensors-ot-delete 2 params → 200400401403429500
POST
/sensors/{type}/linking-key
Generate linking key
sensors-ot-linking-key-generate 1 param → 200400401403429500

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are OT_Connectors_Sensor-Object (9 properties), OT_Connectors_sensor-update-request-body (3 properties), OT_Connectors_ErrorResponse (3 properties), OT_Connectors_sensor-list-response (3 properties). Each schema is shown below with its type and property counts.

OT_Connectors_Sensor-Object
object
9 properties
OT_Connectors_sensor-create-request-body
object
3 properties 3 required
OT_Connectors_sensor-list-response
object
3 properties
OT_Connectors_sensor-linking-key-create-response
object
2 properties
OT_Connectors_ErrorResponse
object
3 properties
OT_Connectors_sensor-update-request-body
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tenable-ot-connectors-api-openapi.yml Raw ↑

Other APIs Tenable publishes across the network.

Tenable About API
Tenable Access Control (API) API
Tenable Access Control (Groups) API
Tenable Access Control (Permissions) API
Tenable Access Control (Roles) API
Tenable Access Control (Users) API
Tenable Access Groups v1 API
Tenable Access Groups v2 API
Tenable Account Groups API
Tenable Accounts API
Tenable Activity Log API
Tenable AD object API
Where this information came from

This is an independent, third-party profile of Tenable OT Connectors API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.