Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.7331.org/llms.txt

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

​
1. Log In

Portal uses platform-delivered one-time codes — no passwords. You sign in via a platform you already have (Discord, Telegram, …) and the bot DMs you a code.
1

Start at the portal

Go to portal.7331.org/auth. Returning users type their username; new users skip straight to platform selection.
curl -X POST https://portal-api.7331.org/v1/authentication/lookup \
  -H "Content-Type: application/json" \
  -d '{"username": "championoftheworld"}'
2

Request a code

Pick a platform. The API generates an IP-bound login code and hands it to the bot, which DMs it to you.
curl -X POST https://portal-api.7331.org/v1/authentication/request \
  -H "Content-Type: application/json" \
  -d '{"platform": "discord", "platform_user_id": "123456789012345678"}'
3

Verify

Paste the code. On success, the server sets psession and — for new users — auto-creates an account with a random username you can change later via POST /v1/users/me/update.
curl -X POST https://portal-api.7331.org/v1/authentication/verify \
  -H "Content-Type: application/json" \
  -d '{"code": "ABCD1234"}'

​
2. Open a Chat

Chats come in four flavors:
  • OFFICIAL — admin-curated, visible to everyone
  • PUBLIC — user-created, listed with a vanity slug
  • PRIVATE — owner + invited members only
  • DIRECT — ephemeral 1-on-1 chat created by the matcher
Browse the public list at portal.7331.org, or use GET /v1/portal/chats to fetch it programmatically. Premium users can create their own chats.

​
3. Get Matched (Optional)

If you just want to talk to someone new, skip chat creation and enqueue: 
curl -X POST https://portal-api.7331.org/v1/portal/match/enqueue \
  -H "Cookie: psession=…" \
  -d '{"interest": "any"}'
The matcher pairs you into a direct chat the moment another user is online. Leave with POST /v1/portal/match/leave or just disconnect — a 60s grace window protects against reloads.

​
Next Steps

Authentication

Session cookies, API keys, and the two OTP flows.

API Reference

Every endpoint, grouped by surface.