HTTP API snapshot 0.9.17-patch1
This reference covers four selected HTTP operations from the stored 0.9.17-patch1 WebRTC OpenAPI snapshot. Use it to inspect that snapshot's request fields, responses and authentication requirements. It is not the complete TelAPI reference or a fresh export of the current platform release.
The snapshot's version is independent of your selected platform guide. Confirm the API contract for your deployed release before building an integration; these pages do not establish compatibility with 0.9.17-patch2 or Next.
Choose an operation
| Task | Operation |
|---|---|
| Obtain a session ID and WebSocket token | POST /api/v1/sessions/token |
| Discover an endpoint's interaction capabilities | GET /api/v1/runtime/capabilities |
| List endpoints available to the API-key team | GET /api/v1/endpoints |
| Read the team's TTS character usage | GET /api/v1/usage/tts-characters |
The ChannelMessage envelope describes the top-level message schema named by the token operation. It does not define all nested payload contracts.
Availability and access
The platform administrator controls API availability through FEATURE_API_ACCESS. The WebRTC export profile enables API access and WebRTC; this stored snapshot documents that profile. Your deployment may enable different features. Confirm access with your administrator when an operation is unavailable.
Each operation declares team API-key authentication in the X-API-Key header and documents its required scope. Having a key does not imply permission for every operation or endpoint. Endpoint runtime capabilities determine which interaction modes are available.
Reading the schemas
Field tables summarize properties; “required” is relative to the containing object. Expand the exact request or response schema for all constraints, alternatives and examples. Error responses shown here are schema declarations; runtime error handling has not been verified by this preview.
The snapshot contains generic property-level error examples that can differ from the example for a particular HTTP status. Prefer the status-specific example when inspecting that response, and do not treat either example as an exhaustive error-code list. Missing descriptions remain explicitly identified rather than filled with inferred behavior.
Download the selected OpenAPI operations or search this API snapshot. The download contains only the operations and supporting definitions listed here. Use your deployment's API origin; no development server is prescribed by this subset.