API Reference

Connect to the API

Use this base URL for all public gateway requests. Prefix your bot routes with /bots/management or /bots/utilities to avoid conflicts.

curl -i https://api.tennesseemanagement.xyz/api/health

Bot connectivity: An online gateway only confirms this Express app is running. The Management and Utilities routes also require their own backend URLs to be configured and reachable.

Authentication

Each bot authenticates its own requests. Sign in using the appropriate bot's login endpoint and then send the returned JWT as a Bearer token to protected endpoints. The Utilities Bot may instead require Discord OAuth depending on its configuration.

curl -X POST https://api.tennesseemanagement.xyz/bots/management/api/admin/login \
  -H "Content-Type: application/json" \
  -d '{"password":"YOUR_DASHBOARD_PASSWORD"}'

curl https://api.tennesseemanagement.xyz/bots/management/api/admin/servers \
  -H "Authorization: Bearer YOUR_JWT_TOKEN"

Windows PowerShell: The multiline examples use Bash-style \ continuation. In PowerShell use one line, or the PowerShell backtick character for continuation. Never send credentials to a URL that has an invalid HTTPS certificate.

Security: Login endpoints accept POST, not GET. Don't enter credentials into URLs. Don't put your bot tokens, JWT secret, or passwords in this public documentation. Management and Utilities credentials are not interchangeable.

Responses & errors

The gateway forwards JSON responses from the configured bot API. A few errors are generated by the gateway itself.

Endpoints

Search by route, method, service, or description. Expand an endpoint to see a request example. An endpoint appearing here does not guarantee its upstream bot is currently online.