Authentication
Create, use, and understand team API keys — and what they cannot access.
Authentication
The public API authenticates exclusively via team API keys with the TP_ prefix.
Create a Key
- You need the Superadmin permission.
- Go to Administration → API Keys.
- Click Create new API key.
- Optionally: choose a description and a team member as context.
- After creation, the key is shown only once — copy it immediately.
Without a linked member, the team owner permissions apply. With a member, module and board permissions follow that member.
UI details: API Keys.
One-time display
If you close the dialog without saving the key, you cannot view it again. You must then reroll it.
Reroll & Delete
- Reroll: generates a new key; the old one becomes invalid immediately.
- Delete: permanently removes the key.
Both actions are only available in the web app — not via the API.
Request with curl
curl -X GET "https://api.team-panel.com/v1/team/get/{teamId}" \
-H "Authorization: Bearer TP_your_key"Replace {teamId} with your team ID and TP_your_key with your API key.
The same key also works for the Remote MCP endpoint. Setup and tools: MCP.
Not Available with API Keys
These areas require session auth, other secrets, or are blocked for integrators:
| Area | Brief reason |
|---|---|
/v1/admin, /v1/auth, /v1/auth-client, /v1/account, /v1/checkout, /v1/notifications, /v1/internal | Session or internal secrets |
/v1/cdn, /v1/voice, /v1/bot, /v1/backupPanel | Infrastructure / other auth |
/v1/gamePanel | Separate server API, not in the public OpenAPI |
/v1/profile, /v1/portalPage, /v1/logs, /v1/modules | Session / UI only |
/v1/team, /v1/team/create, /v1/team/last | User-specific session routes |
/v1/team/invites, owner routes, API key CRUD | Sensitive team administration |
Key management (create, reroll, delete), auth, admin, checkout, and enabling/disabling modules are not possible via API keys.