Create an API token in the current account.
This V2 endpoint generates tokens that use _ (underscore) as the separator
between the token ID and the secret string, instead of the $ separator
used by the V1 endpoint. For example: 42_a1b2c3d4...
Tokens created via this endpoint are fully compatible with all existing authentication mechanisms.
API key for authentication. Make sure to include the word apikey, followed by a single space and then your token.
Example: apikey 1234$abcdef
Account ID.
API token name.
"My token"
Date when the API token becomes expired (ISO 8086/RFC 3339 format), UTC. If null, then the API token will never expire.
"2021-01-01T12:00:00.000000Z"
API token role.
API token description.
"It's my token"
OK.
API token name.
"My token"
Date when the API token becomes expired (ISO 8086/RFC 3339 format), UTC. If null, then the API token will never expire.
"2021-01-01T12:00:00.000000Z"
API token role and issuer data.
API token ID.
42
Deletion flag. If true, then the API token was deleted.
false
Expiration flag. If true, then the API token has expired. When an API token expires it will be automatically deleted.
false
Date when the API token was issued (ISO 8086/RFC 3339 format), UTC.
"2021-01-01T12:00:00.000000Z"
Date when the API token was last used (ISO 8086/RFC 3339 format), UTC.
"2021-01-01T12:00:00.000000Z"
API token with _ separator.
Copy it, because you will not be able to get it again.
We do not store tokens. All responsibility for token storage and usage is on the issuer.
"42_a1b2c3d4e5f6..."
API token description.
"It's my token"