🔑 Authentication and access¶
Authentication tokens are used to enable access to the API without rate-limits or data limits. This takes a format like
ubxbhwera9xkmx4yoej6yt5tslvpjcdj. Each client uses one or more tokens to connect to the APIs, as each is associated with a set of permissions.
Whilst the token is optional, anonymous users get limited, rate-limited data.
Use of the API without a token is not recommended in production as access may be rate-limited, and extended data may not be returned for any given query.
We ask that users consuming the API in anonymous mode provide a link in their product back to the DeviceIdentifier API’s product page.
Obtaining a token¶
Authentication is performed using a token provided by Reincubate, which can be obtained by contacting email@example.com.
Authenticating with a token¶
If one had a token of
ubxbhwera9xkmx4yoej6yt5tslvpjcdj, it could be used by setting the HTTP
Authorization header to
Token ubxbhwera9xkmx4yoej6yt5tslvpjcdj. Like so:
$ wget https://di-api.reincubate.com/v1/gsma-imeis/352073069165968/ --header="Authorization: Token ubxbhwera9xkmx4yoej6yt5tslvpjcdj" -qSO - --content-on-error
The client libraries include their own documentation, and support the token being set via an environment variable, like so:
$ export RI_DEVID_TOKEN='ubxbhwera9xkmx4yoej6yt5tslvpjcdj'