LeanData 🧠 Scheduling Inputs API
The 🧠 Scheduling Inputs API from LeanData — 1 operation(s) for 🧠 scheduling inputs.
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:leandata-scheduling-inputs-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
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 🧠 Scheduling Inputs 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: 🧠 Scheduling Inputs
description: ''
paths:
/v1/scheduling/retrieve-inputs:
post:
tags:
- 🧠 Scheduling Inputs
summary: v1/scheduling/retrieve-inputs
description: 'This endpoint returns the fields defined in your trigger node. Use this endpoint to dynamically determine what prospect data must be collected (including field types and validation rules) prior to calling the routing availability endpoint.
⚠️ Note: Routing Links Trigger Nodes are not supported.
Common use cases:
Agentic scheduling: ask only for missing fields
Dynamic UI: render required fields based on trigger configuration
Request Body Parameters
nodeName (required) — A string value that contains the name of your Trigger Node (in the BookIt Flowbuilder). For more information, check out the Trigger Node Implementation guide.
Response Body Parameters
name — A string name of the requested trigger node.
inputs — An array of input field objects that represent the fields required for routing. Each input field object contains the following properties:
⚠️ Note: All input definitions in the inputs array are configured in the LeanData application. If any updates or changes are needed—such as adding, removing, or modifying input fields—they must be made in the corresponding configuration within LeanData. These definitions cannot be modified through the API.
name — A string that represents the unique API name of the input field. This value should be used as the key when submitting data for booking or routing requests.
type — A string that represents the expected data type of the input field.
Supported values include:
STRING — A text value
PHONE — A text value of the phone number (can include country code).
DOUBLE — A numeric value (supports decimal values)
BOOLEAN — A true/false value'
requestBody:
content:
application/json:
schema:
type: object
example:
nodeName: New Webform Prospect
responses:
'200':
description: Successful response
content:
application/json: {}
operationId: postV1SchedulingRetrieveInputs
x-operation-id-source: derived