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

InfluxDB Telegrafs API

The Telegrafs API from InfluxDB — 8 operation(s) for telegrafs.

InfluxDB Telegrafs API is one of 40 APIs that InfluxDB publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

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

This API exposes 14 operations across 8 paths, and defines 19 schemas. It is described by OpenAPI 3.2.0.

Requests are made against the base URL https://cloud2.influxdata.com/api/v2.

14 operations 8 paths 19 schemas 4 DELETE5 GET4 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
Base URL
https://cloud2.influxdata.com/api/v2
Authentication
HTTP Basic, API Key
Resource Areas
1

Authentication & Security 2

InfluxDB Telegrafs API declares 2 security schemes for authenticating requests. It accepts HTTP basic authentication (BasicAuthentication). An API key is passed in the header as Authorization (TokenAuthentication). By default, every request must be authenticated.

  • BasicAuthentication — Basic authentication scheme Use the HTTP Basic authentication scheme for InfluxDB /api/v2 API operations that support it: Syntax Authorization: Basic BASE64ENC…
  • TokenAuthentication — Use the [Token authentication](section/Authentication/TokenAuthentication) scheme to authenticate to the InfluxDB API. In your API requests, send an Authorizat…

Paths & Operations 14

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

Telegrafs 14
GET
/api/v2/telegrafs
List all Telegraf configurations
GetTelegrafs 2 params → 200default
POST
/api/v2/telegrafs
Create a Telegraf configuration
PostTelegrafs 1 param body → 201default
DELETE
/api/v2/telegrafs/{telegrafID}
Delete a Telegraf configuration
DeleteTelegrafsID 2 params → 204default
GET
/api/v2/telegrafs/{telegrafID}
Retrieve a Telegraf configuration
GetTelegrafsID 3 params → 200default
PUT
/api/v2/telegrafs/{telegrafID}
Update a Telegraf configuration
PutTelegrafsID 2 params body → 200default
GET
/api/v2/telegrafs/{telegrafID}/labels
List all labels for a Telegraf config
GetTelegrafsIDLabels 2 params → 200default
POST
/api/v2/telegrafs/{telegrafID}/labels
Add a label to a Telegraf config
PostTelegrafsIDLabels 2 params body → 201default
DELETE
/api/v2/telegrafs/{telegrafID}/labels/{labelID}
Delete a label from a Telegraf config
DeleteTelegrafsIDLabelsID 3 params → 204404default
GET
/api/v2/telegrafs/{telegrafID}/members
List all users with member privileges for a Telegraf config
GetTelegrafsIDMembers 2 params → 200default
POST
/api/v2/telegrafs/{telegrafID}/members
Add a member to a Telegraf config
PostTelegrafsIDMembers 2 params body → 201default
DELETE
/api/v2/telegrafs/{telegrafID}/members/{userID}
Remove a member from a Telegraf config
DeleteTelegrafsIDMembersID 3 params → 204default
GET
/api/v2/telegrafs/{telegrafID}/owners
List all owners of a Telegraf configuration
GetTelegrafsIDOwners 2 params → 200default
POST
/api/v2/telegrafs/{telegrafID}/owners
Add an owner to a Telegraf configuration
PostTelegrafsIDOwners 2 params body → 201default
DELETE
/api/v2/telegrafs/{telegrafID}/owners/{userID}
Remove an owner from a Telegraf config
DeleteTelegrafsIDOwnersID 3 params → 204default

Schemas 19

The contract defines 19 schemas that model the data the API accepts and returns. The most detailed are TelegrafPluginRequest (6 properties), TelegrafRequest (5 properties), Error (4 properties), Label (4 properties). Each schema is shown below with its type and property counts.

ResourceOwner
ResourceMembers
object
2 properties
Link
string
URI of resource.
TelegrafPluginRequest
object
6 properties
LabelsResponse
object
2 properties
Label
object
4 properties
Telegrafs
object
1 property
Error
object
4 properties 1 required
ResourceOwners
object
2 properties
ErrorCode
string
code is the machine-readable error code.
TelegrafRequest
object
5 properties
LabelResponse
object
2 properties
AddResourceMemberRequestBody
object
2 properties 1 required
ResourceMember
Labels
array
Links
object
URI pointers for additional paged results.
3 properties 1 required
Telegraf
object
LabelMapping
object
A label mapping contains a label ID to attach to a resource.
1 property 1 required
UserResponse
object
4 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

influxdb-telegrafs-api-openapi.yml Raw ↑

Other APIs InfluxDB publishes across the network.

InfluxDB Authorizations (API tokens) API
InfluxDB Bucket Schemas API
InfluxDB Buckets API
InfluxDB Cells API
InfluxDB Checks API
InfluxDB Config API
InfluxDB Dashboards API
InfluxDB Data I/O endpoints API
InfluxDB DBRPs API
InfluxDB Delete API
InfluxDB Invokable Scripts API
InfluxDB Labels API
Where this information came from

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