# Influxdb 2 API Authorization

**URL:** <https://community.influxdata.com/t/influxdb-2-api-authorization/9957>\
**Category:** InfluxDB 2\
**Tags:** influxdb, feedback\
**Created:** [May 31, 2019, 6:24am UTC](https://community.influxdata.com/t/influxdb-2-api-authorization/9957 "2019-05-31T06:24:44Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ChappIO](https://sea1.discourse-cdn.com/flex023/user_avatar/community.influxdata.com/chappio/32/3108_2.png) [@ChappIO](https://community.influxdata.com/u/ChappIO)\
**Post date:** [May 31, 2019, 6:24am UTC](https://community.influxdata.com/t/influxdb-2-api-authorization/9957/1 "2019-05-31T06:24:44Z")

</div>

I have been playing around with the Influx 2 alpha and noticed you use the **Token** type for authorization. I was wondering if this was a conscious decision or just a type that was picked.

The reason I ask is that it is not a formally recognized authorization type. Most commonly the **Bearer** type is used for token authorization. I suspect that people who use HTTP clients and SDK generators might find some difficulty because of this deviation from convention.