LeanData 📆 Meetings > Manage API
The 📆 Meetings > Manage API from LeanData — 1 operation(s) for 📆 meetings > manage.
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/leandata-meetings-manage-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: LeanData BookIt 📆 Meetings > Manage API
description: Programmatic scheduling, availability lookup, and meeting management for the LeanData BookIt scheduling product. Power custom UIs with server-to-server access to availability, round-robin, and meeting CRUD.
version: 1.0.0
servers:
- url: https://api.leandata.com
tags:
- name: 📆 Meetings > Manage
description: ''
paths:
/v1/meeting/:meetingId:
patch:
tags:
- 📆 Meetings > Manage
summary: v1/meeting/:meetingId
description: '<p>This endpoint is used to reschedule an existing meeting by providing a new start and end time.</p>
<p>💡 The <code>:meetingId</code> path parameter should be replaced with the unique ID of the meeting you want to update.</p>
<hr />
<h4 id="request-body-parameters">Request Body Parameters</h4>
<ul>
<li><p><code>scheduledTime</code> (required) — An <strong>object</strong> that defines the selected meeting time.</p>
<ul>
<li><p><code>start_time</code> (required) — A <strong>number</strong> representing the meeting start time in Unix epoch milliseconds.</p>
</li>
<li><p><code>end_time</code> (required) — A <strong>number</strong> representing the meeting end time in Unix epoch milliseconds.</p>
</li>
<li><p><code>timezone</code> — A <strong>string</strong> in IANA format (e.g. <code>America/Los_Angeles</code>). This value is used solely for <strong>formatting</strong> the confirmation email sent to the prospect. The actual meeting time is determined using the raw timestamps.</p>
</li>
</ul>
</li>
</ul>
<hr />
<h4 id="response-body-parameters">Response Body Parameters</h4>
<ul>
<li><p><code>meetingId</code> — A <strong>string</strong> representing the unique identifier for the booked meeting.</p>
</li>
<li><p><code>organizerEmail</code> — A <strong>string</strong> containing the email address of the assigned rep who will host the meeting.</p>
</li>
</ul>
'
requestBody:
content:
application/json:
schema:
type: object
example:
scheduledTime:
start_time: 1746547200000
end_time: 1746548100000
timezone: America/Los_Angeles
parameters:
- name: Content-Type
in: header
schema:
type: string
example: application/json
responses:
'200':
description: Successful response
content:
application/json: {}
delete:
tags:
- 📆 Meetings > Manage
summary: v1/meeting/:meetingId
description: '<p>This endpoint cancels a previously scheduled meeting. It requires only the meeting ID in the URL path—no request body is needed.</p>
<p>A successful cancellation returns a <code>200 OK</code> status. There is no response body.</p>
'
responses:
'200':
description: Successful response
content:
application/json: {}