# Turnix

> Turnix (turnix.io) is a managed, globally distributed TURN/STUN service for WebRTC. A backend requests short-lived ICE credentials with POST https://turnix.io/api/v1/credentials/ice (Bearer API token, server-side only) and passes the returned iceServers to RTCPeerConnection.

Every docs page is available as Markdown by appending .md to its URL. Ready-made prompts for coding agents: https://turnix.io/docs/getting-started/ai-agents.md

## Getting started

- [Introduction](https://turnix.io/docs/getting-started.md): Turnix is a managed, globally distributed TURN/STUN service for WebRTC. Learn how TURN and STUN fit into WebRTC and how Turnix works end to end.
- [Quickstart](https://turnix.io/docs/getting-started/quickstart.md): Get working TURN/STUN servers into your WebRTC app in five minutes. Create a project and API token, request ICE credentials from your backend, and pass them to RTCPeerConnection.
- [Build with AI agents](https://turnix.io/docs/getting-started/ai-agents.md): Turnix is AI ready. Copy-ready prompts for Claude Code, Cursor and other coding agents to integrate Turnix TURN/STUN in seconds, for web apps, Flutter, Node.js, Nextcloud Talk, Jitsi Meet and coturn migrations.

## Concepts

- [Credentials & TTL](https://turnix.io/docs/concepts/credentials.md): How Turnix ICE credentials are created, what the TTL controls, when credentials expire, and how to refresh them for new connections and ICE restarts.
- [Regions & geo-routing](https://turnix.io/docs/concepts/regions.md): How Turnix picks a TURN region for each credential request (GeoIP, preferred_region, fixed_region), how to forward the end user's IP, and which regions your plan can use.
- [Clients & rooms](https://turnix.io/docs/concepts/clients-rooms.md): Label Turnix credential requests with initiator_client, receiver_client and room to trace calls, participants and TURN sessions in the dashboard.
- [Usage, limits & billing](https://turnix.io/docs/concepts/usage-limits.md): How Turnix measures relayed traffic per billing period, what happens when you reach your plan's limit (HTTP 429), how overage works, and how to monitor usage via the API.

## SDKs

- [JavaScript / Node.js](https://turnix.io/docs/sdks/javascript.md): Use the turnix-js SDK to request Turnix ICE credentials from a Node.js backend and pass them to RTCPeerConnection in the browser.
- [Dart / Flutter](https://turnix.io/docs/sdks/dart.md): Use the turnix_dart package to request Turnix ICE credentials from a Dart backend and use them with flutter_webrtc.

## Integrations

- [Shared-secret credentials (LTC)](https://turnix.io/docs/integrations/shared-secret.md): Use a Turnix per-project auth secret with software that generates TURN REST API credentials itself, such as Nextcloud Talk, Jitsi Meet and coturn-compatible apps.
- [Nextcloud Talk](https://turnix.io/docs/integrations/nextcloud.md): Step-by-step setup of Turnix as the STUN and TURN server for Nextcloud Talk, using a shared auth secret, in the admin UI or with occ.
- [Jitsi Meet](https://turnix.io/docs/integrations/jitsi.md): Step-by-step setup of Turnix as the TURN/STUN server for a self-hosted Jitsi Meet, using Prosody external_services with a shared secret, or static credentials for a quick test.
- [Flutter](https://turnix.io/docs/integrations/flutter.md): Add Turnix TURN/STUN servers to a Flutter WebRTC app with flutter_webrtc - a backend endpoint for ICE credentials, peer connection setup, refresh before expiry and how to verify the relay.

## API reference

- [API overview](https://turnix.io/docs/api-reference.md): Turnix REST API basics - base URL, versioning, Bearer authentication, request and response format, error format and status codes, and usage limits.
- [Authentication](https://turnix.io/docs/api-reference/authentication.md): Authenticate to the Turnix API with project API tokens sent as Bearer tokens. How to create, store, rotate and remove tokens, and authentication errors.
- [Credentials](https://turnix.io/docs/api-reference/credentials.md): POST /api/v1/credentials/ice: create short-lived TURN/STUN credentials for WebRTC. All parameters, headers, the response format, region selection and error codes.
- [Regions](https://turnix.io/docs/api-reference/regions.md): GET /api/v1/regions: list Turnix TURN regions with slug, location and status, for use with preferred_region and fixed_region.
- [Usage](https://turnix.io/docs/api-reference/usage.md): GET /api/v1/usage/current and /usage/list_periods: read your Turnix plan, billing period and relayed traffic in GB.