Skip to main content

Documentation Index

Fetch the complete documentation index at: https://bavlio.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

Bavlio is a sales outreach platform built so AI agents can drive every workflow — from finding leads to personalizing emails to running multi-step campaigns — through a single REST API. These docs are the canonical reference. Every public capability behind your bav_live_ API key is documented here, with copy-paste examples in cURL, Python, and Node, an interactive API reference, and machine-readable specs at /openapi.json for tooling.

​
Get going in 5 minutes

Quickstart

Authenticate, make your first call, handle errors, and build a real outreach loop.

API Reference

Every endpoint with live request examples and response schemas, generated from the OpenAPI spec.

Authentication

bav_live_ API key format, Bearer header, key rotation, x402 wallet auth.

MCP

Wire Bavlio into Claude Desktop, Cursor, and any MCP-compatible agent. Docs MCP live now; API-action MCP on the roadmap.

​
Core capabilities

Campaigns

Create, launch, pause, and resume multi-step outbound campaigns. Per-campaign stats, leads, events, and AI-personalized drafts.

Email Finder & Verification

SMTP-probe candidate emails, verify deliverability, batch-resolve full datasets.

Lead Finder

Resolve names + companies to LinkedIn profile URLs. Batch async with status polling.

BaviMail Proxy

Send transactional email, manage sending domains and aliases, browse inbound replies.

LinkedIn (via Unipile)

Connect LinkedIn accounts, send invites and messages, sync content, manage send limits.

x402 Pay-Per-Call

USDC-on-Base micropayments for unauthenticated agent calls. No account required.

​
Built for agents

The full API is described by an OpenAPI 3.1 spec (190+ endpoints). An /llms.txt index and /llms-full.txt full-content dump are auto-generated for AI ingestion. A docs MCP server is live at bavlio.mintlify.app/mcp for any agent that needs to query these docs as native tools (Claude Desktop, Cursor, etc.).
These docs document what exists today. Where a feature is on the roadmap (Idempotency-Key middleware, customer-registered webhooks, restricted API keys), the page says so plainly and gives a working alternative until it ships. No aspirational claims.
Once you have an API key, every public capability — campaigns, leads, sender profiles, templates, sends, replies — is invocable from documentation alone. The first key still needs a dashboard login (deliberate: prevents key-from-key minting); after that, agents drive everything.

​
Need help?

Status

API uptime, incident history, scheduled maintenance.

Support

Contact the team for setup, billing, or scoping questions.

Changelog

What’s new, deprecations, breaking changes.