Skip to main content

TURN Server REST API

The Metered TURN Server REST API lets you programmatically create, enable / disable, label, rotate, and scope TURN credentials while monitoring real‑time and historical usage.

You can also create credential that auto-expire after a fixed period of time.

Instead of manually issuing static long‑lived credentials, you can automate short‑lived or project‑scoped keys, enforce least‑privilege access, and cleanly isolate environments (staging vs production) or customers.

Core use cases include:

  • Dynamic generation of TURN credentials for each session or tenant
  • Enforcing security by rotating or disabling leaked credentials instantly
  • Tracking bandwidth / relay usage globally or per project / user for cost control
  • Separating traffic with project API keys for cleaner quota management and analytics

Below you can find grouped links to every credential, usage, and project operation.

Table of Contents

Credential & Management

Usage

Projects

Authentication

Credential API Key

The Get Credential API API's that require the TURN Credential API key, this API is unique to the TURN Credentials.

And it is visible using in the "Show API Key" button next to the TURN Credential and you can use this API Key in the front-end as well as it is credential scoped.

Secret Key

All the other API's uses the secret key for authentication, the secret key should never be exposed on the front-end, to access the secret key you can go to Dashboard -> Developers there you will find the Secret Key.

Secret Key should never be exposed in the Front End and must always be used by your back-end server-side application.

Project API Key

For some project scoped API endpoints you can also use the project key, the project key is project scoped and is different for each project. So if you don't want to use the acccount scoped secret key you can also use the project scoped project key.

You can read more about Projects here