Developer partner workflow
Build a reliable Meeto integration from the first test to production
Choose the right widget surface, keep public and server credentials in the right places, connect call events to your product and test booking or room flows before a customer depends on them.
Choose the smallest integration surface
| Product stack | Starting point |
|---|---|
| Static HTML or server-rendered site | HTML loader or Web Component from @meeto/embed-core |
| React or Next.js | @meeto/embed-react with a client boundary for interactive controls |
| Vue or Nuxt | @meeto/embed-vue and an origin-locked public key |
| Angular | @meeto/embed-angular with event callbacks wired to the host UI |
| WordPress | Meeto plugin or shortcode; see the WordPress integration guide |
Start with the framework-agnostic quickstart if the product stack is still undecided. Add a framework package only when the host application needs typed props or lifecycle events.
Developer partner starter checklist
- Create a test key. In the widget dashboard, add localhost or a staging origin. Add the final production origin only when it is known.
- Render a visible container. Give an inline widget a responsive height, or choose a bubble when the product needs a floating call entry point.
- Wire the lifecycle. Handle ready, joined, participants, left and error states. Show a useful fallback when the browser blocks camera or microphone access.
- Keep secrets server-side. Put API and host credentials in the server environment. The public
mk_live_…key can appear in browser code because it is origin-locked. - Test two participants. Use another browser or device, check mobile layout, reload during pre-join and confirm the host application responds when someone leaves.
- Document the support boundary. Record the allowed origins, package version, room semantics, current plan limits and who owns the Meeto account after launch.
Use the React guide or WordPress guide when you need a tested integration example rather than a framework-neutral snippet.
Connect booking and server-side workflows carefully
Use a public booking page when a guest should choose availability, submit details and receive meeting information for that appointment. Use a shared widget room for an always-open support or sales destination.
Browser surface
The widget joins the room and emits lifecycle events. Keep the public key and UI configuration in the browser, and never treat a shared room as a private queue.
Server boundary
Use a server route for operations that need an API or host secret. Add idempotency to retried appointment creation and validate the input before forwarding it.
Guest hand-off
Show the resulting booking or join URL clearly, explain camera and microphone permissions and retain a non-media contact path for failures.
API examples and endpoint availability can change. Check the current developer documentation and test against the production account before promising an automated workflow to a customer.
Agree attribution and services before launch
Implementation, maintenance and support are services a developer can offer under their own agreement. Meeto subscription pricing, referral rewards and reseller arrangements are separate.
There is no published commission rate, automatic affiliate payout, white-label entitlement or guaranteed lead attribution on this page. Ask for written terms covering eligibility, attribution window, refunds and payment timing before publishing a referral campaign.
Email Meeto about a developer pilot or read the general partner information.
Frequently asked questions
Which Meeto SDK should an integrator start with?
Use the framework-agnostic loader or Web Component for a plain site, @meeto/embed-react for React or Next.js, @meeto/embed-vue for Vue or Nuxt and @meeto/embed-angular for Angular. The developer docs list the current packages and event surface.
Is the embed key a secret?
No. The mk_live_… embed key is a public, origin-locked key intended for browser code. Keep API credentials and host secrets on your server, and allow only the production origins that should load the widget.
Can an integration create private meeting links?
Use a booking page when a guest should choose a time and receive appointment-specific meeting details. Server-side API workflows can create meetings with a secret credential; do not expose that credential in a client bundle. Confirm the current API contract in the developer documentation before shipping it.
Can developers offer Meeto as a white-label component?
Do not promise white-label output. Meeto branding remains visible in the widget. Developers can build an integration or implementation service, while any reseller, referral or co-marketing terms must be agreed in writing first.
Are developer referrals automatically attributed?
There is no published automatic affiliate payout or attribution programme on this page. Ask Meeto to confirm any referral rules in writing before using a referral link or making a commercial claim.
Put it to work
Open your Meeto account to set it up, or explore the working product first.