Connect · BAMF Developer Platform
Connect API Contract
How Connect keeps a clean api.bamf.ai contract, stable resource naming, and clear product-facing endpoints.
Connect should publish one stable contract at api.bamf.ai.
Public docs should teach Connect routes, Connect resource names, fulfillment mode, and Connect-only enrichments first.
On this page
- Read the Connect contract first
- Match the request to the right Connect surface
- Return Connect-shaped resources
Agent discovery
Related documentation
- BAMF Developer Docs - Build creator workflows with the BAMF REST API, Product MCP, playbooks, local agent kits, and agent-discoverable docs.
- Connect Overview - BAMF Developer Docs - Public overview of the Connect CRM, outreach ops, MCP, browser skills, and client-portal surface.
- Client Portal Integration - BAMF Developer Docs - How the canonical bamf.com client workspace links to BAMF.ai Connect docs while keeping private portal operations in BAMF OS.
- Connect API - BAMF Developer Docs - Campaign, lead, conversation, tagging, and qualification endpoints for the Connect CRM surface.
- Campaign Stats & Queues - BAMF Developer Docs - Branded BAMF metrics, queue health, and campaign scoreboard endpoints for connection rate, reply rate, warm-lead flow, and operator visibility.
- CRM Tags & Qualification - BAMF Developer Docs - How Connect classifies leads, applies CRM tags, and keeps warm-lead, cold-lead, and needs-response queues accurate.