Create a token

    Tokens are visible to the user who created the token. Users who own a token with Operator permissions also have access to all tokens. Tokens stop working when the user who created the token is deleted.

    We recommend creating a generic user to create and manage tokens for writing data.

    To manage InfluxDB API Tokens in the InfluxDB UI, navigate to the API Tokens management page.

    Load Data

    1. From the API Tokens management page, click Generate and select a token type (Read/Write Token or All Access API Token).
    2. In the window that appears, enter a description for your token in the Description field.
    3. If generating a read/write token:
      • Search for and select buckets to read from in the Read pane.
      • Search for and select buckets to write to in the Write pane.
    4. Click Save.

    Use the to create a token. Include flags with the command to grant specific permissions to the token. See the available flags. Only tokens with the write: authorizations permission can create tokens.

    Create an All-Access token

    Create an All-Access token to grant permissions to all resources in an organization.

    1. influx auth create \
    2.   --org my-org \

    Create an Operator token

    Create a token with specified read permissions

    1. influx auth create \
    2.   --org my-org \
    3.   --read-bucket 03a2bbf46309a000 \
    4.   --read-bucket 3a87c03ace269000 \
    5.   --read-dashboards \
    6.   --read-tasks \
    7.   --read-telegrafs \
    8.   --read-user

    See the influx auth create documentation for information about other available flags.

    Use the /api/v2/authorizations InfluxDB API endpoint to create a token.

    Include the following in your request:

    1. INFLUX_ORG_ID=YOUR_ORG_ID
    2. INFLUX_TOKEN=YOUR_API_TOKEN
    4. curl -v --request POST \
    5.   http://localhost:8086/api/v2/authorizations \
    6.   --header "Authorization: Token ${INFLUX_TOKEN}" \
    7.   --header 'Content-type: application/json' \
    8.   --data '{
    9.   "status": "active",
    10.   "description": "iot-center-device",
    11.   "orgID": "'"${INFLUX_ORG_ID}"'",
    12.   "permissions": [
    13.     {
    14.       "resource": {
    15.         "orgID": "'"${INFLUX_ORG_ID}"'",
    16.         "type": "authorizations"
    18.     },
    19.     {
    20.       "action": "read",
    21.       "resource": {
    22.         "orgID": "'"${INFLUX_ORG_ID}"'",
    23.         "type": "buckets"
    24.       }
    25.     },
    26.     {
    27.       "action": "write",
    28.       "resource": {
    29.         "orgID": "'"${INFLUX_ORG_ID}"'",
    30.         "type": "buckets",
    31.         "name": "iot-center" 
    32.       }
    33.     }
    34.   ]

    Create a token scoped to a user

    See the POST /api/v2/authorizations documentation for more information about options.