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

Tanium Destinations API

Manage connection destinations

Tanium Destinations API is one of 22 APIs that Tanium publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Destination. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, and a getting-started guide.

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

Requests are made against a single base URL, https://{tanium_server}.

5 operations 2 paths 3 schemas 1 DELETE2 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Server
https://{tanium_server}
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Tanium Destinations API declares 1 security scheme for authenticating requests. An API key is passed in the header as session (apiToken). By default, every request must be authenticated.

  • apiToken — API token passed in the session header for authenticating with the Tanium Connect API.

Paths & Operations 5

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

Destinations 5

Manage connection destinations

GET
/plugin/products/connect/v1/destinations
List All Destinations
listDestinations → 200401
POST
/plugin/products/connect/v1/destinations
Create A New Destination
createDestination body → 200400
GET
/plugin/products/connect/v1/destinations/{destinationId}
Get A Destination By ID
getDestination 1 param → 200404
PUT
/plugin/products/connect/v1/destinations/{destinationId}
Update A Destination
updateDestination 1 param body → 200400404
DELETE
/plugin/products/connect/v1/destinations/{destinationId}
Delete A Destination
deleteDestination 1 param → 200400404

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are Destination (6 properties), DestinationCreate (3 properties), Error (2 properties). Each schema is shown below with its type and property counts.

Error
object
2 properties
DestinationCreate
object
3 properties 3 required
Destination
object
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tanium-destinations-api-openapi.yml Raw ↑

Other APIs Tanium publishes across the network.

Tanium API Gateway
Tanium Actions API
Tanium Alerts API
Tanium Authentication API
Tanium Connections API
Tanium Events API
Tanium Evidence API
Tanium File Downloads API
Tanium File Operations API
Tanium Groups API
Tanium Intel Documents API
Tanium Labels API
Where this information came from

This is an independent, third-party profile of Tanium Destinations 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.