API Reference
Look up exact signatures, types and endpoints. There are two kinds of reference:
- HTTP APIs for server-side calls that need no SDK, such as creating rooms.
- SDK references generated from each package, for exact props, types and methods.
For step-by-step integration, start with the Quickstart or your SDK guide.
HTTP APIs
All HTTP calls authenticate with Authorization: Bearer <api-username>:<api-key> and belong on your server, never in a browser or mobile app.
| Task | Endpoint | Guide |
|---|---|---|
| Every resource: fields, examples, responses and errors | https://mediasfu.com/v1/… | HTTP API reference |
| Create, join or end a room | POST https://mediasfu.com/v1/rooms | Rooms API |
| Stream in and out with WHIP, WHEP and HLS | /v1/meetings/:meetingID/… | Streaming |
| Add participants that publish and receive over HTTP | /v1/meetings/:meetingID/external-sessions | Participants over HTTP |
| Control AI calls from your server | AI call-control endpoints | AI call control |
| Try any request live | API Sandbox |
SDK references
| Package | Best for | API docs |
|---|---|---|
mediasfu-shared | Shared core logic across frameworks | Open API reference |
mediasfu-reactjs | Web apps with full React control | Open API reference |
mediasfu-angular | Angular apps with DI-based wrappers | Open API reference |
mediasfu-reactnative | Bare React Native mobile apps | Open API reference |
mediasfu-reactnative-expo | Expo-managed mobile apps | Open API reference |
mediasfu-vue | Vue apps with composition-friendly APIs | Open API reference |
mediasfu_sdk | Flutter apps across mobile, web, and desktop | Open staged Dartdoc and pub.dev |
com.mediasfu:mediasfu-sdk-android / com.mediasfu:mediasfu-sdk | Native Android and KMP Compose apps | Open staged Dokka/KDoc and Maven Central |
| MediaSFU Swift | Native iOS apps with Swift/UIKit/SwiftUI entry points | Apple SDK README and USAGE.md |
| MediaSFU Unity | Unity apps, games, simulations, and interactive 3D experiences | Unity SDK README and API contract |
How to choose the right reference
- Start with SDK Guides when you are choosing a package or setting up a first room.
- Use this overview when you know the package family but need the right reference destination.
- Open Generated API Docs when you need exact generated TypeDoc, Dartdoc, or Dokka/KDoc pages.
- Open Choose your UI mode when you are deciding between prebuilt UI, UI overrides, custom components, or headless mode.
Recommended reading order
- Start with /sdks to choose the right framework package.
- Read the relevant SDK guide for quickstart, backend mode, and framework-specific setup.
- Jump into the package API site when you need exact types, method signatures, or generated symbol listings.