POST /v4/user/login

This endpoint authenticates a user and returns an access token for subsequent API requests.

Overview

The login endpoint validates user credentials (email and password) and returns an authentication token upon successful authentication. This token should be used in the Authorization header for all authenticated API requests.

Request Body Parameters

The request accepts a JSON payload with the following parameters:

Parameter	Type	Required	Description
`em`	string	Yes	User's email address
`pass`	string	Yes	User's password

Example Request Body

{
  "em": "user@example.com",
  "pass": "your_password"
}

Response Codes

200 OK

Successful authentication. Returns user data and authentication token.

Response Structure:

{
  "token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...",
  "user": {
    "id": "user_id",
    "email": "user@example.com",
    ...
  }
}

401 Unauthorized

Authentication failed due to invalid credentials.

Response Structure:

{
  "err": 1,
  "errMsg": "AccessDenied",
  "svcs": []
}

Common causes:

Incorrect email address

Incorrect password

Account does not exist

Account may be locked or disabled

Authentication Flow

Send Login Request: POST credentials to /v4/user/login

Receive Token: On success, extract the authentication token from the response

Store Token: Save the token securely (e.g., in an environment variable)

Use Token: Include the token in subsequent API requests using the Authorization header

Usage Notes

Token Storage: Store the returned authentication token in the token environment variable for reuse across requests

Token Expiration: Tokens may expire after a certain period. If you receive 401 errors on authenticated endpoints, re-authenticate to obtain a new token

Security: Never commit credentials or tokens to version control. Use Postman environment variables to manage sensitive data

Rate Limiting: Multiple failed login attempts may result in temporary account lockout

Variables Used

This request uses the following environment variables:

baseUrl - Base API URL

email - User email address

password - User password

curl --location 'https://api.kickbase.com/v4/user/login' \ --header 'Accept: application/json' \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "pass": "password", "em": "username@toplevel.domain" }'

{ "u": { "email": "user@example.com", "notifications": 17407, "cover": "user/123abc.png", "flags": 32, "proExpiry": "1970-00-00T00:00:00Z", "vemail": "user@example.com", "perms": [ 3001, 15 ], "id": "1234", "name": "Player", "profile": "https://kickbase.b-cdn.net/user/123abc.png, "mfacp": [], "uim": "user/123abc.png" }, "srvl": [ { "id": "1234", "cpi": "1", "name": "League", "creator": "Creator", "creatorId": "1234", "creation": "1970-00-00T00:00:00Z", "ai": 0.0, "t": 123, "au": 123, "mu": 123, "ap": 123, "pub": false, "gm": 123, "mpl": true, "pl": 123, "ci": "https://kickbase.b-cdn.net/league/123abc.jpeg", "amd": true, "mpst": 123, "vr": 123, "adm": false, "lim": "league/123abc.jpeg", "uim": "user/123abc.jpeg" }, ], "tkn": "string", "tknex": "1970-00-00T00:00:00Z", "chttkn": "string", "chtknex": "1970-00-00T00:00:00Z", "isnu": false, "isnr": false }

User Login#

Overview#

Request Body Parameters#

Example Request Body#

Response Codes#

200 OK#

401 Unauthorized#

Authentication Flow#

Usage Notes#

Variables Used#

Request

Responses

User Login