LeanData is a Sunnyvale, California revenue orchestration platform built on the Salesforce ecosystem. The company is best known for inventing lead-to- account matching and lead routing for B2B revenue teams; its managed package on the Salesforce AppExchange has been deployed by more than 1,000 B2B companies including Uber, Palo Alto Networks, Shopify, Zoom, New Relic, Snowflake, and DocuSign. The current platform spans four product lines — Orchestration (lead/contact/account routing, deduplication, SLAs, signal workflows), BookIt (forms, handoff, and links-based scheduling), Buying Groups (multi-stakeholder pipeline and engagement), and Revenue Insights (reporting and analytics). LeanData exposes four developer APIs that wrap the platform's core capabilities — the Matching API (real-time lead / contact / account identification from external systems), the Round Robin API (advanced weighted distribution, working hours, and vacation-aware assignment), the BookIt API (scheduling inputs, availability, and meeting CRUD for custom UIs), and the Graph API (one-time routing and routing-graph metadata for custom orchestration). The Matching and Round Robin APIs are Salesforce-native and dispatched through the managed package's Apex REST endpoint at /services/apexrest/LeanData/LeanDataAPI, authenticated with the customer's own Salesforce OAuth 2.0 Connected App; BookIt and Graph are hosted at api.leandata.com behind AWS API Gateway and authenticated with a server-side API key in an X-Api-Key header. Since the Q2 2026 release LeanData also runs a hosted BookIt MCP server at https://mcp.leandata.com/mcp — currently labelled beta — which exposes BookIt scheduling and operational data to MCP-compatible AI clients under OAuth 2.1 with PKCE and dynamic client registration, with admin, user and partner scopes and tool visibility filtered by the caller's BookIt permission set. Developer documentation is published as a public Postman collection at docs.leandata.com. Commercial offerings are tiered across Standard, Advanced, Premium, and Enterprise editions of Orchestration plus BookIt scheduling products and Buying Groups, with implementation services billed separately.
LeanData publishes 9 API contracts indexed on the APIs.io network, including 🗓️ Availability API, Legacy (still supported) API, Matching API, and 6 more. Tagged areas include Revenue Operations, Lead Routing, Lead to Account Matching, Salesforce, and Sales Engagement.
The LeanData catalog on APIs.io includes 1 Spectral governance ruleset.
LeanData’s developer surface includes developer portal, documentation, changelog, pricing, training material, engineering blog, YouTube channel, and 60 more developer resources.
Regulatory Posture applies to this provider. Its tags matched the
Horizontal (data, software, accessibility, platform) regime, so
Regulatory Posture carries 15 points of the composite.
If this regime is wrong for your business, say so on your
provider repo — the
applicability map is public and we will correct it.
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it
carries 10 points of the composite. It is scored from the published contracts
themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already
holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in
front of it, and the first time that check is skipped a duplicate record is created.
Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet,
not penalised by it.
The six quality facets above are damped to 75 points between them,
because the conditional facet above carries the other
25. That is why each facet's contribution is shown against a damped
maximum: raising a quality facet moves the composite by 75% of its nominal
weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site.
It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/leandata/"><img src="https://apis.io/badge/leandata/card.svg" alt="LeanData on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
Idempotency+9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented) Ask about this →
Typed Event Surface+6 pts — AsyncAPI document, OR webhooks/callbacks objects in the as-published OpenAPI, OR common[].type includes Webhooks Ask about this →
Agentic Commerce Well-Known Document+5 pts — a parsing /.well-known/ucp.json or acp.json declaring a version and at least one service, OR (0.27) a live x402 payment challenge from _data/x402-adoption.json — `self` when its endpoints are on the provider's own domain, `platform` when they are on a vendor's Ask about this →
Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.
Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →
The Kin Score Market layer reads a provider inside its market:
its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted:
not part of the Kin Score or agent readiness.
Registered MCP server and declares compatibility are report only — not weighted.
Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.
The availability endpoints return meeting configuration and open time slots used to render booking pages or refresh availability. Depending on the request context (routing, dire...
This section outlines the endpoints used to retrieve scheduling data for building a custom calendaring experience. Both endpoints return the same structure of read-only information
This section describes the endpoints used to trigger 1x Routing for creating a custom orchestration experience, as well as to retrieve the status of the resulting job. When invo...
This section outlines the endpoints used to retrieve Routing Graphs information for building a custom orchestration experience. The endpoint returns information such as trigger ...
LeanData ships a hosted, remote BookIt MCP server, announced in the Q2 2026 release. It exposes BookIt scheduling and operational data to any MCP client (Claude, ChatGPT, Agentf...
Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.
aid: leandata
name: LeanData
description: LeanData is a Sunnyvale, California revenue orchestration platform built on the Salesforce ecosystem. The company
is best known for inventing lead-to- account matching and lead routing for B2B revenue teams; its managed package on the
Salesforce AppExchange has been deployed by more than 1,000 B2B companies including Uber, Palo Alto Networks, Shopify, Zoom,
New Relic, Snowflake, and DocuSign. The current platform spans four product lines — Orchestration (lead/contact/account
routing, deduplication, SLAs, signal workflows), BookIt (forms, handoff, and links-based scheduling), Buying Groups (multi-stakeholder
pipeline and engagement), and Revenue Insights (reporting and analytics). LeanData exposes four developer APIs that wrap
the platform's core capabilities — the Matching API (real-time lead / contact / account identification from external systems),
the Round Robin API (advanced weighted distribution, working hours, and vacation-aware assignment), the BookIt API (scheduling
inputs, availability, and meeting CRUD for custom UIs), and the Graph API (one-time routing and routing-graph metadata for
custom orchestration). The Matching and Round Robin APIs are Salesforce-native and dispatched through the managed package's
Apex REST endpoint at /services/apexrest/LeanData/LeanDataAPI, authenticated with the customer's own Salesforce OAuth 2.0
Connected App; BookIt and Graph are hosted at api.leandata.com behind AWS API Gateway and authenticated with a server-side
API key in an X-Api-Key header. Since the Q2 2026 release LeanData also runs a hosted BookIt MCP server at https://mcp.leandata.com/mcp
— currently labelled beta — which exposes BookIt scheduling and operational data to MCP-compatible AI clients under OAuth
2.1 with PKCE and dynamic client registration, with admin, user and partner scopes and tool visibility filtered by the caller's
BookIt permission set. Developer documentation is published as a public Postman collection at docs.leandata.com. Commercial
offerings are tiered across Standard, Advanced, Premium, and Enterprise editions of Orchestration plus BookIt scheduling
products and Buying Groups, with implementation services billed separately.
x-docs-platform: postman
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-10-03
tags:
- Revenue Operations
- Lead Routing
- Lead to Account Matching
- Salesforce
- Sales Engagement
- Sales Productivity
- Marketing Operations
- Scheduling
- Meeting Booking
- Account Based Marketing
- Buying Groups
- Signal Orchestration
- Go-To-Market
- CRM
- AppExchange
tags_raw:
- Revenue Operations
- Lead Routing
- Lead to Account Matching
- Salesforce
- Sales Engagement
- Sales Productivity
- Marketing Operations
- Scheduling
- Meeting Booking
- Account Based Marketing
- Buying Groups
- Signal Orchestration
- Go to Market
- RevOps
- GTM
- CRM
- AppExchange
type: Index
deliveryModel:
model: saas
open_source: false
commercial: true
callable_host: true
label: Hosted service · you call their endpoint
confidence: high
source:
- openapi
- pricing
generated: '2026-08-28'
method: derived
accessModel:
pricing: paid
onboarding: unknown
trial: false
try_now: false
public: false
label: Paid
confidence: high
source:
- plans
- authentication
- scopes
- rate-limits
- security
generated: '2026-11-13'
method: derived
position: Producing
access: 3rd-Party
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/leandata.png
url: https://raw.githubusercontent.com/api-evangelist/leandata/refs/heads/main/apis.yml
created: '2026-05-25'
modified: '2026-08-13'
specificationVersion: '0.23'
apis:
- aid: leandata:leandata-availability-api
name: LeanData 🗓️ Availability API
description: '<p>The availability endpoints return meeting configuration and open time slots used to render booking pages
or refresh availability. Depending on the request context (routing, direct link, or reschedule), the response includes
meeting details, eligible hosts, and available time windows.</p>
<ul>
<li><p><strong>POST</strong> <code>/v1/scheduling/route-and-fetch-availability</code></p>
</li>
<li><p><strong>POST</strong> <code>/v1/scheduling/fetch-availability</code></p>
</li>
</ul>'
humanURL: https://docs.leandata.com
baseURL: https://api.leandata.com
tags:
- Availability
tags_raw:
- 🗓️ Availability
properties:
- type: OpenAPI
url: openapi/leandata-availability-api-openapi.yml
- type: Overlay
url: overlays/leandata-availability-overlay.yaml
- type: Documentation
url: https://docs.leandata.com
- aid: leandata:leandata-legacy-still-supported-api
name: LeanData Legacy (still supported) API
description: '<p>This section outlines the endpoints used to retrieve scheduling data for building a custom calendaring
experience. Both endpoints return the same structure of <strong>read-only</strong> information—including scheduling metadata,
working hours, available time slots, and configured users—that can be used to render the scheduling page.</p>
<ul>
<li><p><strong><code>v1/scheduling/retrieve-info</code></strong> — Use this endpoint <strong>when booking a meeting</strong>
<strong>for the first time</strong>.</p>
</li>
<li><p><strong><code>v1/scheduling/retrieve-modification-info</code></strong> — Use this endpoint <strong>when modifying
an existing meeting</strong>, such as rescheduling or canceling.</p>
</li>
</ul>
<p>These endpoints provide all the data needed to power the UI for selecting a meeting time and pre-populating prospect
details.</p>'
humanURL: https://docs.leandata.com
baseURL: https://api.leandata.com
tags:
- Legacy (still supported)
properties:
- type: OpenAPI
url: openapi/leandata-legacy-still-supported-api-openapi.yml
- type: Overlay
url: overlays/leandata-legacy-still-supported-overlay.yaml
- type: Documentation
url: https://docs.leandata.com
- aid: leandata:leandata-matching-api
name: LeanData Matching API
description: The Matching API from LeanData — 1 operation(s) for matching.
humanURL: https://docs.leandata.com
baseURL: https://yourinstance.my.salesforce.com
tags:
- Matching
properties:
- type: OpenAPI
url: openapi/leandata-matching-api-openapi.yml
- type: Overlay
url: overlays/leandata-matching-overlay.yaml
- type: Documentation
url: https://docs.leandata.com
- aid: leandata:leandata-meetings-create-api
name: LeanData 📆 Meetings > Create API
description: '<p>Use these endpoints to finalize and book meetings after a timeslot has been selected.</p>
<p>⚠️ <strong>Important:</strong> You <strong>must</strong> support both <code>POST /v1/meeting</code> and <code>POST
/v1/round-robin-meeting</code>.</p>
<p>The correct endpoint is determined by the availability response:</p>
<ul>
<li><p>If <code>pageInfo.displayAllPoolAvailability = true</code>, you must book using <code>POST /v1/round-robin-meeting</code>.</p>
</li>
<li><p>If <code>pageInfo.displayAllPoolAvailability = null</code> or <code>false</code>, you must book using <code>POST
/v1/meeting</code>.</p>
</li>
</ul>
<p>This behavior is driven by your scheduling graph configuration and cannot be assumed ahead of time.</p>'
humanURL: https://docs.leandata.com
baseURL: https://api.leandata.com
tags:
- 📆 Meetings > Create
properties:
- type: OpenAPI
url: openapi/leandata-meetings-create-api-openapi.yml
- type: Overlay
url: overlays/leandata-meetings-create-overlay.yaml
- type: Documentation
url: https://docs.leandata.com
- aid: leandata:leandata-meetings-manage-api
name: LeanData 📆 Meetings > Manage API
description: The 📆 Meetings > Manage API from LeanData — 1 operation(s) for 📆 meetings > manage.
humanURL: https://docs.leandata.com
baseURL: https://api.leandata.com
tags:
- 📆 Meetings > Manage
properties:
- type: OpenAPI
url: openapi/leandata-meetings-manage-api-openapi.yml
- type: Overlay
url: overlays/leandata-meetings-manage-overlay.yaml
- type: Documentation
url: https://docs.leandata.com
- aid: leandata:leandata-meetings-retrieve-api
name: LeanData 📆 Meetings > Retrieve API
description: The 📆 Meetings > Retrieve API from LeanData — 2 operation(s) for 📆 meetings > retrieve.
humanURL: https://docs.leandata.com
baseURL: https://api.leandata.com
tags:
- 📆 Meetings > Retrieve
properties:
- type: OpenAPI
url: openapi/leandata-meetings-retrieve-api-openapi.yml
- type: Overlay
url: overlays/leandata-meetings-retrieve-overlay.yaml
- type: Documentation
url: https://docs.leandata.com
- aid: leandata:leandata-one-time-routing-api
name: LeanData One Time Routing API
description: '<p>This section describes the endpoints used to trigger 1x Routing for creating a custom orchestration experience,
as well as to retrieve the status of the resulting job. When invoked, the 1x Routing endpoint returns basic job metadata—including
the <code>jobId</code>—which can be used to check the job’s status.</p>
<ul>
<li><p><code>orchestration/v1/one-time-routing</code> — Use this endpoint to invoke 1x routing for a particular SFDC org</p>
</li>
<li><p><code>orchestration/v1/one-time-routing/:jobId</code> — Use this endpoint to retrieve the job status of a 1x routing
for a particular SFDC org</p>
</li>
</ul>
<p>❗️ <strong>Important:</strong> The API does <strong>not</strong> validate FlowBuilder graphs before triggering routing.
If you invoke 1x Routing to an invalid or misconfigured graph, the request will still be processed—but routing will fail
silently. No error response will be returned from the API.<br />✅ To avoid unexpected behavior, please ensure the graph
is valid and functioning as expected within the LeanData application before using it in API-triggered routing.</p>'
humanURL: https://docs.leandata.com
baseURL: https://api.leandata.com
tags:
- One Time Routing
properties:
- type: OpenAPI
url: openapi/leandata-one-time-routing-api-openapi.yml
- type: Overlay
url: overlays/leandata-one-time-routing-overlay.yaml
- type: Documentation
url: https://docs.leandata.com
- aid: leandata:leandata-retrieve-routing-graphs-information-api
name: LeanData Retrieve Routing Graphs Information API
description: '<p>This section outlines the endpoints used to retrieve Routing Graphs information for building a custom orchestration
experience. The endpoint returns information such as trigger node names, the edges in those trigger nodes, graph name,
etc</p>
<ul>
<li><code>orchestration/v1/routing-graphs</code> — Use this endpoint <strong>when fetching routing graphs</strong> from
a particular SFDC org.</li>
</ul>'
humanURL: https://docs.leandata.com
baseURL: https://api.leandata.com
tags:
- Retrieve Routing Graphs Information
properties:
- type: OpenAPI
url: openapi/leandata-retrieve-routing-graphs-information-api-openapi.yml
- type: Overlay
url: overlays/leandata-routing-graphs-overlay.yaml
- type: Documentation
url: https://docs.leandata.com
- aid: leandata:leandata-scheduling-inputs-api
name: LeanData 🧠 Scheduling Inputs API
description: The 🧠 Scheduling Inputs API from LeanData — 1 operation(s) for 🧠 scheduling inputs.
humanURL: https://docs.leandata.com
baseURL: https://api.leandata.com
tags:
- 🧠 Scheduling Inputs
properties:
- type: OpenAPI
url: openapi/leandata-scheduling-inputs-api-openapi.yml
- type: Overlay
url: overlays/leandata-scheduling-inputs-overlay.yaml
- type: Documentation
url: https://docs.leandata.com
common:
- type: TrustCenter
url: security/leandata-trust-center.yml
- type: AgenticAccess
url: agentic-access/leandata-agentic-access.yml
- type: DomainSecurity
url: security/leandata-domain-security.yml
- type: Website
url: https://www.leandata.com
- type: Portal
url: https://docs.leandata.com
name: LeanData API Documentation
- type: Documentation
url: https://docs.leandata.com
- type: Documentation
url: https://api.leandatainc.com
name: Legacy Matching API Documentation
- type: SupportPortal
url: https://leandatahelp.zendesk.com
name: LeanData Help Center
- type: SupportPortal
url: https://support.leandata.com
name: LeanData Support
- type: ChangeLog
url: https://leandatahelp.zendesk.com/hc/en-us/sections/360002566353-Release-Notes
- type: Pricing
url: https://www.leandata.com/pricing/
- type: Plans
url: plans/leandata-plans-pricing.yml
- type: RateLimits
url: rate-limits/leandata-rate-limits.yml
- type: FinOps
url: finops/leandata-finops.yml
- type: Product
url: https://www.leandata.com/platform/
name: LeanData Platform
- type: Product
url: https://www.leandata.com/platform/orchestration/
name: Orchestration
- type: Product
url: https://www.leandata.com/platform/bookit/
name: BookIt
- type: Product
url: https://www.leandata.com/platform/buying-groups/
name: Buying Groups
- type: Integrations
url: https://www.leandata.com/platform/integrations/
- type: Customers
url: https://www.leandata.com/customers/
- type: Training
url: https://www.leandata.com/learning-center/
name: Learning Center
- type: Training
url: https://www.leandata.com/certification/
name: LeanData Certification
- type: Resources
url: https://www.leandata.com/resources/
- type: Blog
url: https://www.leandata.com/blog/
- type: Forums
url: https://www.opsstars.com/
name: OpsStars Community
- type: AppExchange
url: https://appexchange.salesforce.com/listingDetail?listingId=a0N3000000B4HCREA3
name: LeanData on Salesforce AppExchange
- type: Company
url: https://www.leandata.com/company/
- type: Careers
url: https://www.leandata.com/careers/
- type: Contact
url: https://www.leandata.com/contact/
- type: Newsroom
url: https://www.leandata.com/press/
- type: TrustCenter
url: https://trust.leandata.com/
name: LeanData Trust Center (SafeBase)
- type: TrustCenter
url: security/leandata-trust-center.yml
name: Trust center profile
- type: PrivacyPolicy
url: https://www.leandata.com/privacy/
- type: TermsOfService
url: https://www.leandata.com/terms-of-service/
- type: LinkedIn
url: https://www.linkedin.com/company/leandatainc/
- type: Twitter
url: https://twitter.com/leandatainc
- type: YouTube
url: https://www.youtube.com/@leandatainc
- type: GitHubOrganization
url: https://github.com/leandata
- type: Authentication
url: authentication/leandata-authentication.yml
name: X-Api-Key (BookIt, Graph); Salesforce OAuth 2.0 Connected App (Matching, Round Robin); OAuth 2.1 (BookIt MCP)
- type: DeveloperPortal
url: https://docs.leandata.com
name: LeanData API Documentation
- type: APIReference
url: https://docs.leandata.com
name: LeanData API reference (Postman documenter)
- type: GettingStarted
url: https://docs.leandata.com
name: Get Started with the LeanData APIs
- type: Postman
url: https://www.postman.com/leandata/workspace/leandata-s-public-workspace
name: LeanData's Public Workspace
- type: Support
url: https://support.leandata.com
name: LeanData Support
- type: Login
url: https://login.leandata.com
name: LeanData application login
- type: SignUp
url: https://www.leandata.com/demo-request/
name: Request a demo (no self-service signup)
- type: MCPServer
url: mcp/leandata-mcp.yml
name: LeanData BookIt MCP (remote, https://mcp.leandata.com/mcp)
- type: ToolCrosswalk
url: mcp/leandata-tool-crosswalk.yml
- type: WellKnown
url: well-known/leandata-well-known.yml
- type: LLMsTxt
url: llms/leandata-llms.txt
- type: OAuthScopes
url: scopes/leandata-scopes.yml
- type: Conventions
url: conventions/leandata-conventions.yml
- type: ErrorCatalog
url: errors/leandata-problem-types.yml
- type: DataModel
url: data-model/leandata-data-model.yml
- type: Lifecycle
url: lifecycle/leandata-lifecycle.yml
- type: StatusPage
url: https://status.leandata.com
name: LeanData Status
- type: ChangeLog
url: changelog/leandata-changelog.yml
name: LeanData release history
- type: Conformance
url: conformance/leandata-conformance.yml
- type: Compliance
url: https://trust.leandata.com/
name: SOC 2 Type 2, GDPR, CCPA
- type: VulnerabilityDisclosure
url: security/leandata-vulnerability-disclosure.yml
- type: Security
url: https://trust.leandata.com/?itemUid=64c9680b-ef79-4c92-baa0-13b541954bef
name: Responsible Disclosure
- type: Packages
url: packages/leandata-packages.yml
- type: Components
url: components/leandata-components.yml
- type: AgentSkill
url: skills/_index.yml
- type: Overlay
url: overlays/leandata-availability-overlay.yaml
name: API Evangelist overlays
- type: UsageTerms
url: terms/leandata-terms-of-service.yml
- type: DataProcessing
url: privacy/leandata-privacy-policy.yml
- type: Eligibility
url: eligibility/leandata-eligibility.yml
x-enrichment:
date: '2026-08-13'
status: enriched
artifacts_added: 33
pass: local-v1
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
LeanData API — frequently asked questions
Does LeanData have an API?
Yes. APIs.io lists 9 APIs from LeanData, including LeanData 🗓️ Availability API, LeanData Legacy (still supported) API and LeanData Matching API, and 6 more.
Is there an OpenAPI specification for the LeanData API?
Yes. APIs.io indexes 9 OpenAPI specifications for LeanData, each linked for download from this page.
How do I authenticate with the LeanData API?
LeanData documents its authentication (apiKey/oauth2 · 4 schemes). The details are profiled on APIs.io as LeanData Authentication.
How much does the LeanData API cost?
APIs.io lists 8 pricing plans for LeanData, with each plan's price, limits and inclusions under Pricing on this page.
Does LeanData have an MCP server?
Yes. APIs.io lists 1 MCP server for LeanData: LeanData ships a hosted, remote BookIt MCP server, announced in the Q2 2026 release. It exposes BookIt scheduling and operational data to any MCP client (Claude, ChatGPT, Agentforce, Cursor) and is au
Is the LeanData API ready for AI agents?
LeanData has a Kin Score of 60.2 out of 100 (strong) and an Agent Readiness score of 52.3 (agent-ready), scored by API Evangelist on 2026-11-13.
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.
Kin Score
How this is scored →
It updates itself when the score changes. Paste this where you link to your API docs: