LeanData πŸ“† Meetings > Manage API

The πŸ“† Meetings > Manage API from LeanData β€” 1 operation(s) for πŸ“† meetings > manage.

Operations 2

PATCH /v1/meeting/:meetingId v1/meeting/:meetingId #
DELETE /v1/meeting/:meetingId v1/meeting/:meetingId #

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.
All 92 tools →

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

leandata-meetings-manage-api-openapi.yml Raw ↑
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: 'This endpoint is used to reschedule an existing meeting by providing a new start and end time.


        πŸ’‘ The :meetingId path parameter should be replaced with the unique ID of the meeting you want to update.


        Request Body Parameters


        scheduledTime (required) β€” An object that defines the selected meeting time.


        start_time (required) β€” A number representing the meeting start time in Unix epoch milliseconds.


        end_time (required) β€” A number representing the meeting end time in Unix epoch milliseconds.


        timezone β€” A string in IANA format (e.g. America/Los_Angeles). This value is used solely for formatting the confirmation email sent to the prospect. The actual meeting time is determined using the raw timestamps.


        Response Body Parameters


        meetingId β€” A string representing the unique identifier for the booked meeting.


        organizerEmail β€” A string containing the email address of the assigned rep who will host the meeting.'
      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: {}
      operationId: patchV1Meeting:meetingId
      x-operation-id-source: derived
    delete:
      tags:
      - πŸ“† Meetings > Manage
      summary: v1/meeting/:meetingId
      description: 'This endpoint cancels a previously scheduled meeting. It requires only the meeting ID in the URL pathβ€”no request body is needed.


        A successful cancellation returns a 200 OK status. There is no response body.'
      responses:
        '200':
          description: Successful response
          content:
            application/json: {}
      operationId: deleteV1Meeting:meetingId
      x-operation-id-source: derived