--- title: Slido API Integration on Truto slug: slido category: Event Management canonical: "https://truto.one/integrations/detail/slido/" --- # Slido API Integration on Truto **Category:** Event Management **Status:** Generally available ## MCP-ready AI tools Truto exposes 17 tools for Slido that AI agents can call directly. - **create_a_slido_exports_user** — Start an asynchronous export of users in Slido. Returns a 202 export job object that can be polled for completion. The exported user records include user_id, display_name, email, role, is_active, created_date, joined_date, and modified_date. - **create_a_slido_exports_event** — Start an asynchronous export of events in Slido. Returns an export job object (HTTP 202) with an export_id for polling status via the Get Export endpoint. The exported event records include event_id, owner_user_id, start_date, end_date, timezone, created_date, and modified_date. Accepts an optional filter object in the request body (defaults to empty, exporting all events). - **create_a_slido_exports_room** — Start an asynchronous export of rooms in Slido. Returns an export job object (HTTP 202) with an export_id for polling status via the Get Export endpoint. The exported room records include room_id, event_id, event_owner_user_id, is_active, created_date, and modified_date. Accepts an optional filter object in the request body (defaults to empty, exporting all rooms). - **create_a_slido_exports_participant** — Start an asynchronous export of participants in Slido. Returns an export job object (HTTP 202) for polling export status. The exported participant data includes event_owner_user_id, event_id, participant_id, name, email, user_id, first_joined_date, and modified_date. Accepts an optional participants filter in the request body. - **create_a_slido_exports_question** — Start an asynchronous export of Q&A questions in Slido. Returns an export job object (HTTP 202) with an export_id for polling status via the Get Export endpoint. The exported question records include question_id, event_owner_user_id, event_id, room_id, participant_id, status, is_anonymous, is_starred, score, upvotes, downvotes, highlighted_date, created_date, and modified_date. Accepts an optional filter object in the request body (defaults to empty, exporting all questions). - **create_a_slido_exports_question_reply** — Start an async export of question replies in Slido. Returns: id, type, status, result. The exported data includes question_reply_id, event_id, room_id, question_id, text, status, is_anonymous, is_private, is_pinned, posted_by_moderator, participant_id, created_date, and modified_date per reply. - **create_a_slido_exports_surveys_quizz** — Start an asynchronous export of surveys and quizzes in Slido. Returns an export job object (HTTP 202) with an export_id for polling status via the Get Export endpoint. The exported records include survey_quiz_id, event_owner_user_id, event_id, room_id, type, polls_count, created_date, and modified_date. Accepts an optional filter object in the request body (defaults to empty, exporting all surveys/quizzes). - **create_a_slido_exports_poll** — Start an async export of polls in Slido. Returns: id, type, status, result. Accepted asynchronously (202); use the Get Export endpoint to retrieve the export result. - **create_a_slido_exports_poll_option** — Start an asynchronous export of poll options in Slido. Returns an export job object (HTTP 202) with an export_id for polling status via the Get Export endpoint. The exported poll option records include poll_option_id, event_owner_user_id, event_id, room_id, survey_quiz_id, poll_id, is_correct, order, created_date, and modified_date. Accepts an optional filter object in the request body (defaults to empty, exporting all poll options). - **create_a_slido_exports_poll_vote** — Start an asynchronous poll votes export in Slido. Returns an export job object (202 Accepted) with an export_id for polling status and download URL via the Get Export endpoint. The exported data includes poll_vote_id, event_id, room_id, poll_id, participant_id, is_anonymous, created_date, and modified_date for each poll vote. - **create_a_slido_exports_poll_vote_value** — Start an asynchronous export of individual poll vote values (answer selections) in Slido. Returns an export job object (HTTP 202) with an export_id for polling status via the Get Export endpoint. The exported records include poll_vote_value_id, event_owner_user_id, event_id, room_id, survey_quiz_id, poll_id, poll_vote_id, participant_id, is_anonymous, rating_score, multiple_choice_option_id, quiz_option_id, ranking_option_id, ranking_rank, and modified_date. Accepts an optional filter object in the request body (defaults to empty, exporting all poll vote values). - **create_a_slido_exports_idea_topic** — Start an async export of idea topics in Slido (deprecated — works with the retired Ideas BETA feature; use polls endpoints for the new Ideas poll). Returns: id, type, status, result. The request body accepts an optional filter object that defaults to empty. - **create_a_slido_exports_webex_meeting** — Start an export of Webex meetings in Slido. Returns: id, type, status, result, export_id. The exported data includes event_id, event_owner_user_id, webex_meeting_id, and modified_date. The export is processed asynchronously. - **create_a_slido_exports_space** — Start an async Slido spaces export. Returns the export record including space_id, organization_id, name, description, type, created_date, and modified_date. Accepts an optional filter object in the request body (defaults to empty). - **create_a_slido_exports_spaces_user** — Start an export of Spaces users in Slido. Returns a 202 Accepted response with an ExportOut object for tracking the async export job. The exported data includes space_id, organization_id, user_id, created_date, and modified_date. - **get_single_slido_export_by_id** — Get details of a specific export in Slido by its export id. Returns the export object including its export_id, type, and status. Required: id. - **list_all_slido_exports** — List all Slido exports. Returns a list of export objects including export_id and type. Optional: type to filter exports by export type. ## How it works 1. **Link your customer's Slido 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 Slido.** The Proxy API is a 1-to-1 mapping of the Slido 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 - **Route webinar-qualified leads into your marketing automation** — Marketing platforms can pull Slido participant data and poll responses after each webinar to match attendees to CRM records, spike lead scores based on intent-signaling answers, and trigger follow-up sequences automatically. - **Archive Q&A and poll data for compliance and eDiscovery** — Compliance SaaS vendors serving regulated industries (finance, healthcare) can automate daily exports of questions, replies, and poll votes across all Slido spaces to meet FINRA, SEC, and HIPAA retention mandates. - **Power employee sentiment analytics from All-Hands meetings** — HR intelligence platforms can ingest anonymous question text, upvote counts, and reply data from recurring internal Slido spaces to run NLP on employee feedback and surface trending organizational concerns. - **Benchmark session engagement in event management platforms** — Event aggregators can correlate Slido event, poll, and question export data with their own registration and attendance figures to produce quantitative engagement scores for each speaker or session. - **Enrich BI dashboards with audience interaction data** — Analytics products can extract poll votes, question activity, and participant identifiers to layer Slido engagement metrics onto existing event ROI and attribution reporting. ## What you can build - **Post-event participant sync** — Trigger participant exports after each Slido event and match emails against your user database to attribute engagement to known contacts. - **Poll response ingestion pipeline** — Extract granular poll vote values — including rating scores and multiple-choice selections — to feed lead scoring, survey analysis, or reporting workflows. - **Q&A archival and sentiment feed** — Export raw question text, replies, upvote/downvote counts, and anonymity flags into your storage layer for NLP processing or compliance retention. - **Async export job orchestration** — Ship a background worker that kicks off Slido exports, polls status via the export ID, and downloads results once complete — without your team writing polling logic. - **Webex meeting correlation** — Pull the webex_meeting_id tied to each Slido session to unify Cisco Webex meeting data with audience interaction records in your product. - **Space-scoped data extraction** — Filter exports to specific Slido spaces so customers can isolate All-Hands, webinar, or training data streams per team or business unit. ## FAQs ### How does Truto handle Slido's asynchronous export model? Slido's Data API uses an async bulk export pattern — you trigger an export (e.g., questions, poll votes, participants), receive an export ID, and poll for completion. Truto exposes both the create export tools and the get_single_slido_export_by_id and list_all_slido_exports endpoints so you can orchestrate the full job lifecycle. ### What data can I extract from Slido today? Through Truto's Slido tools you can export users, events, rooms, participants, questions, question replies, surveys/quizzes, polls, poll options, poll votes, poll vote values, idea topics, Webex meetings, spaces, and spaces users. ### Can I create polls or Q&A sessions in Slido through the integration? No. Slido restricts session and content creation to its own UI and native integrations (like PowerPoint and Webex). The available tools are focused on triggering data exports and retrieving results — this is a read-oriented integration by design. ### How fresh is the data I can pull? Data freshness depends on when you trigger the export. Most integrations run exports post-event or on a recurring schedule (e.g., daily for compliance use cases). Once an export job completes, results reflect the state of Slido at the time the job ran. ### Can I tie anonymous Q&A responses back to known users in my system? Participants marked as anonymous will not expose identifying data — the is_anonymous flag is preserved in question exports. For non-anonymous participants, the participant export ties participant_id to name and email, which you can match against your own user or CRM records. ### How is authentication handled? Truto manages the Slido API credentials, token storage, and refresh flow on behalf of your end users, so you don't have to build or maintain the auth layer yourself. Your users connect their Slido account once through Truto's connection flow. ## Related reading - [Connect Slido to Claude: Analyze Participant Feedback and Surveys](https://truto.one/blog/connect-slido-to-claude-analyze-participant-feedback-and-surveys/) — Learn how to connect Slido to Claude using a managed MCP server. Automate participant feedback analysis, Q&A exports, and survey processing with AI agents. - [Connect Slido to ChatGPT: Sync Polls, Q&A, and Interaction Data](https://truto.one/blog/connect-slido-to-chatgpt-sync-polls-q-a-and-interaction-data/) — Learn how to connect Slido to ChatGPT using a managed MCP server. Automate asynchronous Q&A exports, summarize polls, and query audience interaction data. - [Connect Slido to AI Agents: Automate Engagement and Meeting Exports](https://truto.one/blog/connect-slido-to-ai-agents-automate-engagement-and-meeting-exports/) — Learn how to connect Slido to AI Agents using Truto's /tools endpoint. Master asynchronous exports, polling loops, and rate limit handling for event automation.