--- title: Dyte API Integration on Truto slug: dyte category: Video canonical: "https://truto.one/integrations/detail/dyte/" --- # Dyte API Integration on Truto **Category:** Video **Status:** Generally available ## Unified APIs ### Unified Conferencing API - **Attendees** — The attendees represent the individuals who join the meeting. - **Meetings** — The meeting represents the actual meeting or video call conducted on the platform. ## How it works 1. **Link your customer's Dyte account.** Use Truto's frontend SDK; we handle every OAuth and API key flow so you don't need to create the OAuth app. 2. **Authentication is automatic.** Truto refreshes tokens, stores credentials securely, and injects them into every API request. 3. **Call Truto's API to reach Dyte.** The Proxy API is a 1-to-1 mapping of the Dyte API. 4. **Get a unified response format.** Every response uses a single shape, with cursor-based pagination and data in the `result` field. ## Use cases - **Embed native video interviews in your ATS** — Applicant tracking systems can spin up Dyte meetings automatically when interviews are scheduled, assigning recruiters and candidates distinct permission presets — all without leaving the platform or managing Dyte's auth flow directly. - **Power in-app telehealth consultations with accurate billing** — Practice management and telehealth platforms can provision Dyte video rooms for patient appointments, track participant join/leave events, and calculate exact consultation durations for automated invoicing. - **Orchestrate sales call recordings for coaching and analytics** — Sales enablement and CRM platforms can create Dyte meetings for prospect calls, retrieve recordings and transcripts post-call, and surface them in coaching dashboards — treating Dyte as interchangeable infrastructure alongside other conferencing providers. - **Run virtual classrooms from your EdTech product** — Learning platforms can programmatically create meetings for live classes, add instructors and students as attendees with role-appropriate permissions, and track attendance for completion reporting. - **Normalize conferencing data across multiple video providers** — SaaS products that support both Dyte and other conferencing tools can use Truto's Unified Conferencing API to read and write Meetings and Attendees through a single schema, eliminating provider-specific code paths. ## What you can build - **One-click meeting provisioning from scheduled events** — Automatically create a Dyte meeting room whenever an appointment, interview, or class is booked in your application, using the unified Meetings resource. - **Role-based attendee management with auth tokens** — Add participants to a Dyte meeting with specific presets (Host, Speaker, Viewer) via the unified Attendees resource, and receive back the auth tokens needed to render the call in your UI. - **Real-time attendance tracking dashboard** — Listen for participant join and leave events to build a live attendance view and calculate per-participant meeting duration for compliance or billing. - **Post-meeting recording and transcript ingestion** — Fetch composite recordings and AI-generated transcripts after a meeting ends and surface them inside your product's activity feed or analytics module. - **Unified conferencing analytics across providers** — Aggregate meeting counts, attendee participation, and duration metrics from Dyte alongside other video providers through a single normalized data model. ## FAQs ### What Unified API resources does Truto support for Dyte? Truto maps Dyte to the Unified Conferencing API, which includes the Meetings and Attendees resources. Specific tools for Dyte are built on request — contact Truto to enable yours. ### How does authentication work for end users connecting their Dyte accounts? Dyte uses Organization-level API keys (an Organization ID and API Key pair) for server-to-server auth. Your end users provide these credentials through Truto's managed auth flow, so you never handle raw keys directly. ### Can I create meetings and add attendees through Truto, or is it read-only? The Unified Conferencing API is designed to support both read and write operations on Meetings and Attendees. Since Dyte tools are built on request, confirm the exact supported operations with Truto when your integration is provisioned. ### How does Truto handle Dyte's participant auth tokens? When you add an attendee to a Dyte meeting via the Attendees resource, Dyte generates a unique authToken for that participant. Truto surfaces this token in the API response so your frontend can pass it to Dyte's UI Kit to render the call. ### Does Truto support Dyte webhooks for real-time events? Dyte provides webhooks for events like meeting.started, participant.joined, participant.left, and meeting.ended. Truto can normalize these into its eventing layer — discuss your webhook requirements when the integration is configured. ### Are there rate limits I should be aware of? Dyte enforces rate limits on its REST API that vary by plan. Truto respects these limits and handles retries, but you should check your Dyte plan's specific thresholds to size your workloads appropriately.