PPlatformAppStores

Miro Marketplace

Workspace

RealtimeBoard, Inc. (Miro) · Productivity & collaboration suites

Best for: Visual, on-canvas collaboration and diagramming add-ons for Miro boards.

Overview

Miro Marketplace is the distribution channel for apps that extend Miro's collaborative whiteboard. Developers build against the Miro Web SDK for embedded, on-canvas experiences that render widgets and panels, and the Miro REST API for server-side board, item, and webhook automation. All API access uses the OAuth 2.0 authorization-code flow, letting users grant scoped access without sharing credentials. The typical builder is a SaaS vendor adding a Miro surface to an existing product.

Getting listed is gated and heavyweight. Only developers approved through Miro's Partner Interest Form receive a submission link, and every app runs through a multi-week security and design review (roughly 8–12 weeks), enforcing minimal scopes and design guidelines. Miro does not operate native billing — developers implement their own payment flow (Stripe is the documented pattern) and Miro takes no direct cut. Choose Miro Marketplace when your product needs a rich embedded canvas surface and you can invest in a formal partner review cycle.

How to build & ship

  1. 1Create an app in your Miro developer/team settings and get your client credentials
  2. 2Build the in-board experience with the Miro Web SDK and/or automate via the REST API
  3. 3Add OAuth 2.0 with the scopes your app requires and host your app's iframe/backend
  4. 4Test installation and board interactions in a development team
  5. 5Prepare marketplace assets and submit the app for Miro's marketplace review

Key APIs & SDKs

Miro Web SDK (v2)
Miro REST API (v2)
OAuth 2.0 with scopes
Webhooks
App Cards / board item APIs

Integration types

Embedded app
Widget
Connector
Workflow action

Authentication & security

  • Primary auth: OAuth 2.0
  • Also supports: Webhook
  • Security review: Required
  • Only partners approved via the Partner Interest Form may submit; each app undergoes a roughly 8–12 week security and design review.
  • Apps for public listing must meet Miro's marketplace submission requirements and pass a review covering functionality, security, and listing quality before publication; no fixed turnaround is published.
  • Credit-based: 100,000 credits/minute per user-per-app across weighted API levels; 429 on exceed.
Auth docs Store policies

Monetization

Free
Paid app
Onboarding
$0 (approved partners get a complimentary Business plan)
Commission
No native billing; developers process their own payments (Miro takes no direct share)
Merchant of Record
Developer is MoR via their own payment processor

Pros & cons for builders

Pros

  • Access to Miro's large visual-collaboration user base
  • Web SDK enables rich, embedded on-canvas experiences
  • Clear split between in-board (Web SDK) and automation (REST) use cases
  • Modern OAuth-based install flow

Cons

  • Public listing requires meeting a detailed set of submission requirements
  • In-canvas apps require hosting and careful iframe/permission handling
  • Smaller third-party ecosystem than the largest platforms

Frequently asked questions

How do I get my app approved on Miro Marketplace?

Apps for public listing must meet Miro's marketplace submission requirements and pass a review covering functionality, security, and listing quality before publication; no fixed turnaround is published.

What authentication does Miro Marketplace use?

Miro Marketplace apps primarily authenticate with OAuth 2.0, also supporting Webhook.

How is Miro Marketplace monetized?

Miro Marketplace supports Free, Paid app. Typical commission: No native billing; developers process their own payments (Miro takes no direct share). Onboarding fee: $0 (approved partners get a complimentary Business plan).

Is a security review required to list on Miro Marketplace?

Yes, Miro Marketplace requires a formal security or listing review before apps go live. Only partners approved via the Partner Interest Form may submit; each app undergoes a roughly 8–12 week security and design review.