Authentication

How to authenticate with the Chat Service API using JWT tokens and tenant headers.

Overview

All endpoints (except Health) require a Bearer JWT token. The tenantId is extracted from the JWT claims automatically via the @CurrentTenant() decorator.

ECS Fargate Deployment

chat-svc runs on AWS ECS Fargate (not Lambda) with WebSocket support. The staging ALB endpoint is available at https://eventzr-staging-alb-134677813.us-east-1.elb.amazonaws.com/chat/v1

Obtaining a JWT Token

curl -X POST https://535ubezkse.execute-api.us-east-1.amazonaws.com/auth/v1/login \
  -H "Content-Type: application/json" \
  -d '{
    "email": "dev@eventzr.com",
    "password": "Password123!"
  }'

# Response:
# {
#   "data": {
#     "accessToken": "eyJhbGciOiJSUzI1NiIs...",
#     "refreshToken": "eyJhbGciOiJSUzI1NiIs...",
#     "expiresIn": 3600
#   }
# }

Send a message via chat-svcbash

export TOKEN="<access-token-from-response>"

curl -X POST https://eventzr-staging-alb-134677813.us-east-1.elb.amazonaws.com/chat/v1/messages \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -H "x-tenant-id: 00000000-0000-0000-0000-000000000001" \
  -d '{
    "threadId": "<thread-uuid>",
    "content": "Hello from the API!",
    "type": "text"
  }'

Refresh an expired tokenbash

curl -X POST https://535ubezkse.execute-api.us-east-1.amazonaws.com/auth/v1/refresh \
  -H "Content-Type: application/json" \
  -d '{ "refreshToken": "eyJhbGciOiJSUzI1NiIs..." }'

Test Credentials

Staging Environment Credentials

Use these credentials to test the API in the Scalar playground above.

Role	Email	Password	Tenant ID
Developer	`dev@eventzr.com`	`Password123!`	`00000000-...-000001`
Admin	`admin@eventzr.com`	`Password123!`	`00000000-...-000001`

JWT Claims Structure

Decoded JWT payloadjson

{
  "sub": "user-uuid",
  "tenantId": "tenant-uuid",
  "email": "user@example.com",
  "roles": ["user", "organizer", "admin"],
  "planTier": "professional",
  "iat": 1740000000,
  "exp": 1740003600
}

Standard Headers

Header	Required	Description
`Authorization`	Yes	Bearer JWT token
`Content-Type`	POST/PUT/PATCH	application/json
`x-request-id`	No	Request trace ID (UUID), auto-generated if absent
`x-tenant-id`	Recommended	Tenant UUID for explicit tenant filtering
`Idempotency-Key`	No	Idempotency key for write operations (24h TTL)

Response Envelope

Standard response formatjson

{
  "data": { ... },
  "error": null,
  "page": {
    "next_cursor": "eyJwYWdlIjoyLCJsaW1pdCI6MjB9",
    "has_more": true,
    "limit": 20
  },
  "meta": {
    "request_id": "550e8400-e29b-41d4-a716-446655440000",
    "trace_id": "abc123",
    "tenant_id": "tenant-uuid"
  }
}

WebSocket Connection

chat-svc supports real-time messaging via WebSocket (Socket.IO). Connect using the same JWT token for authentication.

Socket.IO connectionjavascript

import { io } from 'socket.io-client';

const socket = io('https://eventzr-staging-alb-134677813.us-east-1.elb.amazonaws.com', {
  path: '/chat/v1/socket.io',
  auth: { token: '<jwt-access-token>' },
  extraHeaders: { 'x-tenant-id': '00000000-0000-0000-0000-000000000001' },
});

socket.on('connect', () => console.log('Connected:', socket.id));
socket.on('message:new', (msg) => console.log('New message:', msg));
socket.on('typing:start', (data) => console.log('Typing:', data));