Developer API

API base URL

Partner integrations should use this base URL for service discovery:

GET https://leadbotapp.com/api/v1 returns JSON with docs_url, openapi_url, and status. CORS allows browser GET from any origin on discovery and OpenAPI routes.

OpenAPI

Download the OpenAPI 3.x document:

Public endpoints

All paths are on https://leadbotapp.com. Dashboard routes (/api/leads, /api/bookings, billing, and auth) require a signed-in session and are not part of the public API.

• GET/api/v1

  Service descriptor (name, version, docs and OpenAPI URLs, status)

• GET/api/v1/openapi.json

  Machine-readable OpenAPI 3.x specification

• GET/api/health

  Deployment health and widget API URL hint

• GET/api/widget/config?business_id={uuid}

  Embeddable widget configuration for a LeadBot business

• POST/api/widget/chat

  Send a chat message in a widget session

• POST/api/widget/leads

  Submit a lead or booking from the widget

• GET/api/marketing/config

  Demo widget config used on leadbotapp.com (not customer-specific)

Authentication

Widget and discovery endpoints are public and scoped by business_id (or the fixed marketing demo). Server-to-server API keys for CRM sync, lead export, and partner automation are included on Business and Agency plans and are rolling out — they are not required for the endpoints listed above.

For connector directory submissions and early partner access, email social@leadbotapp.com.

MCP

A published Model Context Protocol (MCP) server is not available yet. For Meta Muse and similar connector forms, use this page plus the OpenAPI URL above — REST with OpenAPI is our supported public documentation surface today.