JWT Authentication

1. Request Detail

HTTP Method	POST
URL PATH	https://my.gstzen.in/accounts/api/login/token/
Request Payload Type	Form Data
Response Type	application/json

2. Request Payload Example

Form Data

username	example@domain.com
password	********

3. Response Example

Response Example - With valid credentials

{
  "refresh": "eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJ0b2tlbl90eXBlIjoicmVmcmVzaCIsImV4c
    CI6MTcwNzM3NDQ0MCwiaWF0IjoxNzA2NzY5NjQwLCJqdGkiOiJhZmQyNmExMWYwNDA0OGI0YWMzODkyZmY0Y
    TQ3MjAxNCIsInVzZXJfaWQiOjF9.4EFsfqECJdtwZ1mbRo4hElUCYhnYGpgkRbV_gpFoXSk",
  "access": "eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJ0b2tlbl90eXBlIjoiYWNjZXNzIiwiZXhwI
    joxNzA2ODU2MDQwLCJpYXQiOjE3MDY3Njk2NDAsImp0aSI6IjUyOTc0YjFhZjUwYTQ2NDk5NzAyYzA2NjUyN
    GRiMDg2IiwidXNlcl9pZCI6MX0.Cqm4e08K_6Laifz5g2e_0az3HSmFcze2Q0kK1K1Ip0o"
}

With invalid credentials

{
  "detail": "No active account found with the given credentials"
}

Authentication will happen from the GSTZen Portal at /accounts/api/login/token/. This will automatically establish a session. Each user account session is identified by an Authentication Token that gets generated during the profile login. The API token is passed as an authorization bearer token in the HTTP header throughout the entire usage period. Use the generated access token for authentication.

Note: Token is valid for 24hrs.