Authentication

Quick Start with Vercel

For clients to authenticate, the 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

You must replace 9944b09199c62bcf9418ad846dd0e4bbdfc6ee4b with your personal API key.

Obtaining authentication tokens

To obtain a authentication token the fallowing HTTP request has to be performed.

HTTP Request

POST https://api.gsmtasks.com/authenticate/

Query Parameters

Parameter	Type	Required	Description
username	String	yes	The email used during signup
password	String	yes	The password set for that username

Response

{
  "account": "4368ec5d-9942-4c74-90f7-eea752a6e489",
  "token": "7e9917ffg57b043b9527711395c013761b2113c7",
  "accounts": [
    "4368ec5d-9942-4c74-90f7-eea752a6e489",
    "5941c788-f162-4ad0-a43a-4af82bcb30b6"
  ],
  "user": "https://api.gsmtasks.com/users/85410f5f-ec82-4148-ba78-5be5a79f0fb1/"
}

💡

The tokens are valid forever, unless refreshed by the user himself.

Providing an API version

An API version is always expected to have full backwards compatibility. The version is provided by Accept header in the request.

Accept: application/json; version=2.4.36

💡

Without providing the Accept header and a correct version the API will respond with a status code of 400 and an error message.

Introduction Changelog