Tele Developer Guide¶
Tele adds audio and video calls to your product. You keep your users, your login and your UI. Tele provides the rest:
- the call infrastructure (media servers and TURN relays)
- scheduling, invite codes and access control
- call records: duration, participants, IP addresses, participant counts
- persisted in-call chat
- usage metering in room-minutes
Calls hold up to 10 people, so they suit 1:1 support calls, consultations and small team meetings.
How an integration fits together¶
sequenceDiagram
autonumber
participant App as Your app<br/>(web / Flutter / KMP)
participant BE as Your backend<br/>(holds API secret)
participant Tele as Tele API
participant LK as Media server
App->>BE: I'm logged in as user-123
BE-->>App: Tele user token (signed with your secret)
App->>Tele: POST /v1/invites/{code}/join
Tele-->>App: ws_url, media token, ICE servers
App->>LK: connect with the media SDK
Note over Tele,LK: Tele records sessions, chat and room-minutes
- Your backend holds a Tele API key and secret. Only your backend ever sees them.
- Your backend signs a short-lived user token for each logged-in user. The token carries your own
user_id. - Your app calls the Tele API with that token to create calls, preview invites and join.
- Joining returns everything the media SDK needs, and your app connects to the media server directly.
Every participant has a user_id
Tele has no anonymous guests. Every host and every participant is one of your users, identified by your own user_id. That keeps call records, chat history and billing attributable.
What's where¶
| You want to… | Read |
|---|---|
| Make your first call in 10 minutes | Quickstart |
| Understand calls, invites, sessions and billing | Concepts |
| Use a ready-made library for Go, Python, the web, Next.js or Flutter | SDKs |
| Sign tokens from your backend | Authentication |
| Schedule calls and share invite links | Scheduling & invites |
| Connect a client to a call | Joining a call, then Web, Flutter or KMP |
| Add chat | Chat |
| Pull call history and usage reports | Usage & billing |
| Look up an endpoint | API reference |
Environments¶
| Environment | API base URL |
|---|---|
| Production | https://tele-api.cloudguys.io |
| Local development | http://127.0.0.1:8080 |
To get an API key, ask the Tele team. Keys are issued per consumer product.
Open-source SDKs¶
| Library | For |
|---|---|
| tele-go | Go backends |
| tele-fastapi | Python and FastAPI backends |
| tele-ui-pack | The <tele-call> call screen for any web app |
| tele-nextjs-ui | Next.js App Router components |
| tele-flutter | Flutter apps |
Install lines and how they fit together are on the SDKs page. All of them live under github.com/cloudguys-io.