InfluxData Authorizations (API tokens) API
Create and manage authorizations (API tokens).An _authorization_ contains a list of `read` and `write`permissions for organization resources and provides an API token for authentication.An authorization belongs to an organization and only contains permissions for that organization.We recommend the following for managing your tokens:- Create a generic user to create and manage tokens for writing data.- Store your tokens in a secure password vault for future access.### User sessions with authorizationsOptionally, when creating an authorization, you can scope it to a specific user.If the user signs in with username and password, creating a _user session_,the session carries the permissions granted by all the user's authorizations.For more information, see [how to assign a token to a specific user](https://docs.influxdata.com/influxdb/cloud/security/tokens/create-token/).To create a user session, use the [`POST /api/v2/signin` endpoint](#operation/PostSignin).### Related endpoints- [Signin](#tag/Signin)- [Signout](#tag/Signout)### Related guides- [Authorize API requests](https://docs.influxdata.com/influxdb/cloud/api-guide/api_intro/#authentication)- [Manage API tokens](https://docs.influxdata.com/influxdb/cloud/security/tokens/)- [Assign a token to a specific user](https://docs.influxdata.com/influxdb/cloud/security/tokens/create-token/)
InfluxData Authorizations (API tokens) API is one of 45 APIs that InfluxData publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Authorizations (API tokens). The published artifact set on APIs.io includes an OpenAPI specification, an API reference, API documentation, and a getting-started guide.
This API exposes 5 operations across 2 paths, and defines 10 schemas. It is described by OpenAPI 3.2.0, at version 1.0.
Requests are made against a single base URL, /api/v2.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
InfluxData Authorizations (API tokens) API declares
2 security schemes
for authenticating requests.
An API key is passed in the header as Authorization (TokenAuthentication).
It accepts HTTP basic authentication (BasicAuthentication).
By default, every request must be authenticated.
TokenAuthentication— Use the [Token authentication](section/Authentication/TokenAuthentication) scheme to authenticate to the InfluxDB API. In your API requests, send an Authorizat…BasicAuthentication— Basic authentication scheme Use the HTTP Basic authentication scheme for InfluxDB /api/v2 API operations that support it: Syntax Authorization: Basic BASE64ENC…
Paths & Operations 5
Across 2 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 1 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.
Create and manage authorizations (API tokens).
Schemas 10
The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are Resource (5 properties), Error (4 properties), Links (3 properties), Authorizations (2 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from InfluxData 12
Other APIs InfluxData publishes across the network.
This is an independent, third-party profile of InfluxData Authorizations (API tokens) 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.