API Overview
Public TeamPanel API with team API keys and the same /v1 routes as the web app.
API Overview
The public TeamPanel API gives you access to the same /v1/… routes as the web app — authenticated via a team API key.
Base URL
https://api.team-panel.comAuthentication
Send the key in the header:
Authorization: Bearer TP_…Create keys under Administration → API Keys. For details, see API Keys and Authentication.
OpenAPI, Swagger & MCP
| Endpoint | Description |
|---|---|
| https://api.team-panel.com/docs | Swagger UI for the public spec |
| https://api.team-panel.com/openapi.json | Public OpenAPI spec |
| https://api.team-panel.com/mcp | Remote MCP (Streamable HTTP, same API key) |
Rate Limits
- 32 requests / 10 seconds per API key
- Failed authentication: 4 requests / minute per IP
Permissions
Effective permissions follow the optionally linked team member. Without a member, the team owner applies. In addition, you can restrict a key to scopes (e.g. only media:upload). Without scopes, the key has full access within the member's permissions.
Related Pages
- Authentication – create keys, headers, restrictions
- Endpoints – resource prefixes and examples
- Media API – upload files, e.g. screenshots from game servers
- MCP – Remote MCP for AI clients (e.g. Cursor)
Automations
For outgoing webhooks (e.g. Discord), use the Automation module. The public API does not offer incoming webhooks.
GamePanel Server API
The GamePanel server API is separate and not part of the public OpenAPI. It uses its own
middleware and does not appear under /docs or /openapi.json.