Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/raczkodavid/Tikera/llms.txt

Use this file to discover all available pages before exploring further.

The Tikera API uses token-based authentication. Calling POST /api/register or POST /api/login returns a bearer token. Include that token in the Authorization header on every subsequent request that requires authentication.
Each login or registration call invalidates all previous tokens for that account and issues a new one. If you log in from a second location, any earlier token stops working immediately.

​
Register

Create a new user account and receive an authentication token. 
POST /api/register

​
Request body

​
name
string
required
The user’s display name. Maximum 255 characters.
​
email
string
required
A valid, unique email address. Maximum 255 characters.
​
password
string
required
The account password. Minimum 8 characters.
​
password_confirmation
string
required
Must match the password field exactly.

​
Response fields

​
status
string
required
Always "success" on a 201 response.
​
message
string
required
Always "OK" on success.
​
data
object
required

​
Example

curl -X POST http://localhost:8000/api/register \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Ada Lovelace",
    "email": "ada@example.com",
    "password": "secret123",
    "password_confirmation": "secret123"
  }'

{
  "status": "success",
  "message": "OK",
  "data": {
    "user": {
      "id": 1,
      "name": "Ada Lovelace",
      "email": "ada@example.com",
      "role": "user",
      "created_at": "2026-05-14T10:00:00.000000Z",
      "updated_at": "2026-05-14T10:00:00.000000Z"
    },
    "token": "1|abc123..."
  }
}

​
Errors

HTTP statusmessageWhen
422Registration failed due to validation errorsA field is missing, invalid, or email is taken
500Registration failed. Please try again later.Unexpected server error

​
Log in

Authenticate an existing user and receive a fresh token. 
POST /api/login

​
Request body

​
email
string
required
The account’s email address.
​
password
string
required
The account’s password.

​
Response fields

​
status
string
required
Always "success" on a 200 response.
​
message
string
required
Always "OK" on success.
​
data
object
required

​
Example

curl -X POST http://localhost:8000/api/login \
  -H "Content-Type: application/json" \
  -d '{
    "email": "ada@example.com",
    "password": "secret123"
  }'

{
  "status": "success",
  "message": "OK",
  "data": {
    "user": {
      "id": 1,
      "name": "Ada Lovelace",
      "email": "ada@example.com",
      "role": "user",
      "created_at": "2026-05-14T10:00:00.000000Z",
      "updated_at": "2026-05-14T10:00:00.000000Z"
    },
    "token": "2|def456..."
  }
}

​
Errors

HTTP statusmessageWhen
401Invalid credentialsEmail not found or wrong password
500Logon failed. Please try again later.Unexpected server error

​
Pass the token

Include the token in the Authorization header on every protected request: 
Authorization: Bearer {your_token}
Store the token securely. The official client stores it in localStorage under the key "token" and attaches it automatically to every outgoing request.

​
Get the current user

Return the user object associated with the current token. 
GET /api/user
Requires authentication.

​
Response fields

​
status
string
required
Always "success" on a 200 response.
​
data
object
required
The authenticated user object (id, name, email, role, timestamps).

​
Example

curl http://localhost:8000/api/user \
  -H "Authorization: Bearer {your_token}"

{
  "status": "success",
  "message": "OK",
  "data": {
    "id": 1,
    "name": "Ada Lovelace",
    "email": "ada@example.com",
    "role": "user",
    "created_at": "2026-05-14T10:00:00.000000Z",
    "updated_at": "2026-05-14T10:00:00.000000Z"
  }
}

​
Log out

Invalidate the current session token. The token cannot be used after this call. 
POST /api/logout
Requires authentication.

​
Example

curl -X POST http://localhost:8000/api/logout \
  -H "Authorization: Bearer {your_token}"

{
  "status": "success",
  "message": "OK",
  "data": null
}
Only the token used in the request is invalidated. Other tokens belonging to the same user (if any exist) are unaffected — though in practice, logging in always replaces all existing tokens with one new token.

Build docs developers (and LLMs) love

Get started for freeTalk to us