E
API Docs

Seed Data

Pre-populated test data available in the staging environment for development and testing.

Staging Environment

The staging environment is pre-seeded with 3 tenants and 9 user accounts across different roles and subscription tiers. All seed user passwords are Password123!

Tenants (3)

TenantTenant IDTierUsers
T1 - EventZR Platform00000000-0000-0000-0000-000000000001PRO5
T2 - ACME Corp00000000-0000-0000-0000-000000000002ENTERPRISE2
T3 - StartupCo00000000-0000-0000-0000-000000000003STARTUP2

Seed Users (9)

Password for all accounts

Password123!

EmailRolesTenantMFAStatus
partner@eventzr.compartnerT1Noactive
user@eventzr.comuserT1Noactive
organizer@eventzr.comorganizerT1Noactive
admin@eventzr.comadminT1Noactive
dev@eventzr.comdeveloperT1Yesactive
admin@acme.comadminT2Yesactive
user@acme.comuserT2Noactive
admin@startup.coadminT3Noactive
user@startup.couserT3Noactive

Quick Login (Recommended for Testing)

Login as partner (T1, no MFA - gets token directly)bash
curl -X POST "https://535ubezkse.execute-api.us-east-1.amazonaws.com/auth/v1/login" \
  -H "Content-Type: application/json" \
  -d '{"email": "partner@eventzr.com", "password": "Password123!"}'
Login as admin (T3, no MFA)bash
curl -X POST "https://535ubezkse.execute-api.us-east-1.amazonaws.com/auth/v1/login" \
  -H "Content-Type: application/json" \
  -d '{"email": "admin@startup.co", "password": "Password123!"}'

Multi-Tenant Testing

To verify tenant isolation, log in with accounts from different tenants and compare responses. Users from T1 should not see data from T2 or T3.

Cross-tenant isolation testbash
# Get T1 token
T1_TOKEN=$(curl -s -X POST "https://535ubezkse.execute-api.us-east-1.amazonaws.com/auth/v1/login" \
  -H "Content-Type: application/json" \
  -d '{"email": "user@eventzr.com", "password": "Password123!"}' | jq -r '.data.accessToken')

# Get T3 token
T3_TOKEN=$(curl -s -X POST "https://535ubezkse.execute-api.us-east-1.amazonaws.com/auth/v1/login" \
  -H "Content-Type: application/json" \
  -d '{"email": "user@startup.co", "password": "Password123!"}' | jq -r '.data.accessToken')

# Compare profiles - tenantId should differ
curl -s -H "Authorization: Bearer $T1_TOKEN" \
  "https://535ubezkse.execute-api.us-east-1.amazonaws.com/auth/v1/profile" | jq '.data.tenantId'

curl -s -H "Authorization: Bearer $T3_TOKEN" \
  "https://535ubezkse.execute-api.us-east-1.amazonaws.com/auth/v1/profile" | jq '.data.tenantId'