Deployed API — how to reach it. Every command below targets https://auth.dragium.com, the address you used to open this page.
Reachable at auth.dragium.com — the same address as this page. List services:
grpcurl auth.dragium.com list
Inside the container gRPC listens on port 6009, behind the proxy; that port is not reachable from outside.
JWT — sign in for a token, then send Authorization: Bearer <token>. Signin answers with {"Token":"...","Expires":"..."} — the field names are capitalised.
curl -s -X POST https://auth.dragium.com/signin -H 'Content-Type: application/json' -d '{"email":"...","password":"..."}'
End to end:
TOKEN=$(curl -s -X POST https://auth.dragium.com/signin -H 'Content-Type: application/json' -d '{"email":"...","password":"..."}' | jq -r .Token)
grpcurl -H "authorization: Bearer $TOKEN" auth.dragium.com list
Also POST /refresh and POST /validate, on the same address.
These endpoints are served here whether or not a REST API is enabled — a gRPC-only deployment still signs in over HTTP at this address. A 401 from signin means the email matched no user row or the password was wrong; a user row must exist in your user entity with a bcrypt hash in its password column, not a plaintext password.
episodelocationepisode_has_draguserfantasy_seasonseason_has_dragfanstasy_season_has_dragdrag_showuser_has_dragseasondragpassfantasy_leaguefantasy_league_memberfantasy_roster_pickfantasy_weekly_predictionfantasy_score_event