REST API Reference
Together provides a REST API for building integrations, bots, and custom tooling. All API endpoints use JSON request/response bodies and JWT-based authentication.
Base URL
https://your-together-instance.comAuthentication
Most endpoints require a valid JWT access token passed in the Authorization header:
Authorization: Bearer <your_jwt_token>Tokens are obtained through the authentication flow.
Bot Authentication
Bot accounts use a dedicated token authentication mechanism. Bots are created through the admin interface and receive a long-lived API token. Pass it in the Authorization header with a Bot prefix:
Authorization: Bot <your_bot_token>See the Bot API for full documentation.
API Endpoints
Users & Auth
POST /auth/register— Register a new accountPOST /auth/login— Authenticate and receive tokensPOST /auth/refresh— Refresh an expired access tokenGET /users/@me— Get current user profilePATCH /users/@me— Update current user profile
Servers
GET /servers— List servers the user is a member ofPOST /servers— Create a new serverGET /servers/:id— Get server detailsPATCH /servers/:id— Update server settingsDELETE /servers/:id— Delete a server
Channels
GET /servers/:server_id/channels— List channels in a serverPOST /servers/:server_id/channels— Create a channelPATCH /channels/:id— Update channel settingsDELETE /channels/:id— Delete a channel
Messages
GET /channels/:channel_id/messages— List messages in a channelPOST /channels/:channel_id/messages— Send a messagePATCH /messages/:id— Edit a messageDELETE /messages/:id— Delete a message
Search
GET /servers/:id/search— Full-text message search (server-scoped)
ICE
GET /ice-servers— Get TURN/STUN server configuration
Errors
The API uses standard HTTP status codes:
| Status | Meaning |
|---|---|
| 200 | Success |
| 201 | Created |
| 400 | Bad Request |
| 401 | Unauthorized |
| 403 | Forbidden |
| 404 | Not Found |
| 409 | Conflict |
| 500 | Internal Server Error |
Error responses include a JSON body with a message field describing the issue.
Rate Limiting
The API implements rate limiting to prevent abuse. Headers are included in responses:
X-RateLimit-Limit— Maximum requests per windowX-RateLimit-Remaining— Requests remaining in current windowX-RateLimit-Reset— Unix timestamp when the window resets
WebSocket Gateway
For real-time communication, Together uses a WebSocket gateway protocol rather than polling. See the WebSocket Protocol for details.
OpenAPI Specification
A complete OpenAPI 3.0 spec is available at /docs/openapi.yaml.