Most API calls require to be authenticated.
This authentication scheme uses a simple token-based HTTP Authentication scheme. Token authentication is appropriate for API client setups, such as scripts.
The token is associated to a specific User and a specific App.
For clients to authenticate, the auth token key should be included in the Authorization HTTP header.
The key should be prefixed by the string literal "Token", with whitespace separating the two strings.
Authorization: Token 9944b09199c62bcf9418ad846dd0e4bbdfc6ee4b
To get the "Pointzi Auth Token" go to the Pointzi Dashboard Settings and choose from the API Tab
Install Token Authentication¶
Install Token Authentication is a mechanism by which devices an authenticate with the server without the need for a permanent preshared key.
How it works:¶
- Dashboard User generates an token from GET /v3/users/token?installid=xxxxxxx
- The token is then sent to the device using whatever means available (deeplink, simple copy paste from slack, push, sms). See section on token distribution
- The device then uses the intall token in the request header to make authenticated requests.
Tokens by default have a expiry of one hour
Endpoints currently supporting install token v3/tooltips
This is the mechanism by which an install auth token is sent to the device install for which the token is generated. The token is just a simple string it can be distributed to the device using any means by which a string can be published. Deeplink: a deeplink is genererated which is sent to the device through a qr code,push or sms. When the user clicks on the deeplink it willl launch the app and the token will be stored by the app Through slack, this is mostly for testing, the developer can copy the plain token into his slack, and receive it in the device and paste in to the sample app’s text field for entering the token (sdk developers note this text field needs to be provided)