Return the authenticated account and, when available, its plan tier and relevant caps. This is a low-cost authentication check that distinguishes a bad token from an empty calendar. Plan data explains action-specific limits; it does not gate the connection itself.

List the authenticated user's bookable meeting types, including the identifier, duration and host data required for a booking.

Return a meeting type's bookable starts within a date range. The slotsStartUtc values are the starts accepted by booking validation; calendar events alone are not availability.

Create a real appointment for a start present in the meeting type availability results and send invitations. An unlisted start is rejected. A confirmed bookingState means the appointment exists; pending_confirmation means it is not booked yet. Either fullName or both firstName and lastName are required.

Move an appointment to a new start time. Duration is unchanged. Validates availability unless ignoreAvailability is set. A successful response echoes the new time as startUtc.

Cancel an appointment and notify attendees. For a group booking, attendeeId removes one person while cancelAll cancels the whole appointment. Requests with neither are rejected. The response distinguishes attendee_removed from cancelled.

Return appointments with pagination and filters, including the appointmentId needed for changes. Every item carries a confirmed or cancelled status; cancelled items are not upcoming appointments. Pages are 0-indexed.

Return today's appointments for the authenticated user. This specialised query is cheaper and more precise than a general date-filtered appointment list.

Return full detail for one appointment: status, attendees and their attendeeIds, hosts, location and notes. The attendeeIds support guest additions and per-attendee cancellation. The status indicates whether the booking is active.

Add one guest email to an appointment so they receive the invitation and updates. Requires the attendeeId returned with appointment details and accepts one guest per call.

Replace the host-side note on an appointment with call preparation or an outcome summary. This is replacement rather than append, so retained existing text must be included in the new note.

Generate a single-use booking link for a meeting type so someone can choose their own slot. No attendee details are needed and the link cannot be reshared.

Search the CRM by name, email, phone or tag. Results expose contactIds and support duplicate checks before contact creation.

Return a full contact record including linked appointments and form answers. Accepts either a contactId or an attendeeId from an appointment and links booking identity to the stored contact.

Create a CRM contact. Either email or phoneNumber is required. Existing contacts are not deduplicated.

Update a CRM contact. Only supplied fields change. Tags replace the existing list rather than merging, so retained tags must be included.

List connected calendars (Google, Outlook and CalDAV). The result shows whether a host has a calendar attached and supports availability diagnosis.

Send a one-off email to an attendee, such as a follow-up, preparation note or directions. Requires an attendeeId from appointment details. Rate limited to 5 per 5 minutes.

Attach a meeting transcript and/or AI summary in markdown to an appointment. meetergo does not record calls, so the caller supplies the content. Only supplied fields change; null clears one.

Return the full configuration of one meeting type: duration, channel, buffers, booking questions, reminders, host or queue. The result exposes the current values needed for a safe update.

Create a new meeting type owned by the authenticated user. It becomes a real, publicly bookable page immediately. The URL slug is generated from the name and remains editable.

Change a meeting type. Only the fields you send change; everything you leave out keeps its current value.

Delete a meeting type. Its booking page stops working immediately. Existing appointments are not cancelled.

The authenticated user's personal booking page: colours, header image, description, profile links, meeting-type order.

Change branding on the personal booking page. Only the fields you send change. Colours need useCustomColors set, or they are ignored.

Recreate an existing public booking page in meetergo from its URL. Calendly and several other schedulers are recognised automatically. The tool reads only the public profile and creates one meeting type per visible event type with its duration, location and booking questions. It never modifies the source account. Imports are additive, so running it twice creates duplicates. The response lists both created items and failures.

List routing forms and funnels — the qualification forms that route a visitor to the right meeting type or page. Returns 50 at a time; page with offset.

Full definition of a routing form: its steps, fields and the qualifier rules that decide where a visitor is sent.

Create a routing form or funnel. Fields reference existing reusable data fields and qualifiers route on the answers. A qualifier with isFallback true provides the default route.

Update a routing form. Supplying qualifiers, fields or funnelSteps replaces each entire collection, so omitted items are deleted. Leaving those collections out changes only the name, slug or progress bar.

Delete a routing form. Any link already shared stops working.

Send a routing form to one recipient by email or SMS, or just mint the link. The response always carries publicUrl. Rate limited to 20 per minute.

List who a routing form was sent to, with sent, opened or completed status and timestamps. The result identifies recipients who have not answered.

List the reusable form fields shared across routing forms, including fields that may already match a planned addition. Returns 50 at a time with offset pagination.

Create a reusable form field, company-wide. Choice fields need options; text fields do not.

Create many contacts in one import. Each needs email or phoneNumber. A call accepts up to 1000 contacts and the endpoint is limited to 3 calls per minute.

Permanently delete a CRM contact. Their past appointments remain, but the contact record and its form answers are gone.

List webhook endpoints for the company. The result shows current subscriptions against the maximum of six endpoints.

Register an HTTPS endpoint to receive events. Six per company maximum; the API says so plainly when you hit it.

Change a webhook endpoint, its description, or which events it receives. eventTypes replaces the existing list.

Delete a webhook endpoint. Whatever depends on those events stops receiving them immediately.

Return the company's resolved Mira configuration: master switch, assistant profiles, website chat widget including its server-minted publicKey, and data-access toggles. The result is suitable as a rollback snapshot.

Partially update Mira configuration (admin only). Omitted fields keep their current value; webChat merges field-by-field and assistantProfiles replaces the whole list. Saving any webChat field mints the widget publicKey even while enabled stays false, creating a previewable draft state. The response includes previous and current settings for rollback. The API rejects unknown fields.

Roll Mira configuration back to a previously returned settings snapshot. Server-managed fields such as publicKey and the mirrored channels.webChat list are stripped automatically. The minted publicKey survives a rollback and remains harmless while the widget is disabled.

Return the embed snippet a website owner pastes before , plus the preview URL for testing a saved-but-disabled widget. Requires the webChat publicKey minted when widget configuration is first saved.

Start a background crawl of a website into the company's Mira knowledge base, covering its sitemap and same-origin links while extracting, chunking and embedding readable text. Crawl progress remains available through status reads. Re-crawling an unchanged site ingests 0 new pages and is still successful. Requires the file-uploads entitlement (Growth and up).

Progress of the current or last knowledge-base website crawl. { status: "idle" } means none has run yet.

Documents in the company's Mira knowledge base — crawled pages, uploaded files, synced sources — with their source keys.

Remove one document (and its chunks) from the knowledge base. Mira stops answering from it immediately.

Read a sample of a website and propose a complete assistant setup: persona, welcome message, grounded instructions, qualification questions, quick actions, the site's own privacy and imprint links, and a knowledge probe. The result is a settings draft; nothing is stored or configured. Takes up to a minute.

Add a question-and-answer pair to the company's knowledge base in the company's own words. This closes a visitor knowledge gap. Repeating the same question replaces the earlier answer rather than creating two versions.

Summarise recent website assistant activity and the visitor questions it could not answer. Unanswered questions identify gaps suitable for new knowledge entries.

Semantically search the knowledge base using the same retrieval Mira uses for visitor answers. The results validate grounded coverage for a question before launch.

Return the dashboard launch checklist for bookable meeting type, assistant, knowledge, test drive, installation and live state. Each stage includes completion status and the concrete next move, making the result suitable before or after setup changes.

Create a real routing form from supplied qualification questions, with structured fields the company can edit and a fallback rule routing qualified visitors into a meeting type or callback. The returned formId is suitable for a qualifying web chat profile.

Send scripted visitors to the saved assistant, including a buyer, a callback lead and an adversarial visitor, then return pass/fail verdicts with full transcripts. Preview mode creates no bookings or emails and does not require a live widget. The stored result feeds the launch checklist. Takes about a minute and is rate-limited to a few runs per hour.

Fetch a page of the customer's website and verify that it serves both the Mira loader script and the customer's own embed key. Intended after the snippet is installed; installed is true only when both elements are present.