Skip to main content

    4752 Ideas

    David Greenwood
    David GreenwoodContributor

    Add Table name/title to the REST APIOpen

    The REST API returns data_table_format items with no title or name field — every table has a visible name in the Miro UI, but developers can't access it programmatically. What we tried:GET /v2/boards/{id}/items?type=data_table_format — returns tables but no title field. Other item types (sticky notes, shapes, text, cards) all include content/title.GET /v2-experimental/boards/{id}/tables/{id} — has the title, but returns 403 for standard OAuth apps (boards:read boards:write). No additional scope available to unlock it.MCP context_explore — returns generic names like "Table 3458764661623371178" instead of real names. Works for frames/docs but not tables.MCP context_get — the only thing that works. Returns an AI-generated summary where the name appears in prose like titled "Planner Tasks". We extract it with regex.Why this workaround is bad:~10-15s latency per table (AI processes all row data just to produce a summary) Non-deterministic output — same table returns different prose each call; sometimes the name isn't mentioned at all Requires regex against natural language (fragile) No way to ask for "just the title" — context_get only accepts a URL Requires a separate OAuth 2.1 flow (DCR + PKCE) just to connect to MCP Tokens expire hourlyWe're using an AI content analysis tool as a metadata lookup. The data already exists in the Miro backend — it just needs a field on the REST response. The ask: Add a title field to data_table_format items in the v2 API, or make the experimental tables API accessible to standard OAuth apps.

    Feature request: Allow fullscreen, clipboard-write and downloads for trusted iframe embedsOpen

    Hello Miro Team,We are embedding our internal web application inside a Miro board using the Miro embed feature.Our application works correctly when embedded in a standard iframe like this:<iframesrc="https://myapp.com/..."allow="fullscreen; clipboard-write"style="width:100%;height:100%;border:none;"></iframe>In this configuration: Fullscreen API works Clipboard copy works (navigator.clipboard.write) PNG download works via <a download> (Blob URL) However, when embedded via Miro’s embed feature, the generated iframe looks like this:<iframesrc="https://myapp.com/..."sandbox="allow-same-origin allow-scripts allow-forms allow-popups allow-popups-to-escape-sandbox allow-modals allow-storage-access-by-user-activation"allow="encrypted-media"></iframe>In this configuration: Fullscreen is blocked Clipboard API is blocked (Permissions Policy violation) Standard downloads (<a download>) are blocked due to sandbox restrictions We understand and respect the security reasons behind restrictive sandbox and permissions policies for embeds.However, in our case: The embedded application is fully controlled by us. It is hosted on a trusted domain. The intended usage is interactive, not read-only viewing. RequestWould it be possible to support one of the following options: Allow additional permissions for embeds: allow="fullscreen; clipboard-write" sandbox including allow-downloads Provide embed configuration options (checkboxes/toggles) to enable: Fullscreen Clipboard write Downloads Provide a “Trusted Domain Allowlist” feature, where specific domains can be granted expanded iframe permissions. We are not requesting unrestricted access, but rather a secure and controlled way to enable interactive applications inside Miro boards.This would significantly improve integration use cases where embedded tools are meant to be actively used, not just viewed.Thank you for considering this request.Best regards,