Connect · BAMF Developer Platform
Client Portal Integration
How the bamf.com client portal should expose Connect docs, API keys, MCP setup, and shared queue language as one developer surface.
The bamf.com client portal should expose a Developer entry that opens the same BAMF Connect docs and preserves client account context.
The portal and docs should keep one shared vocabulary for scoreboards, queues, qualification tags, and MCP setup.
On this page
- Open Developer from the portal
- Keep key management in the same lane
- Mirror the same object model
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.
- Connect API - BAMF Developer Docs - Campaign, lead, conversation, tagging, and qualification endpoints for the Connect CRM surface.
- Connect API Contract - BAMF Developer Docs - How Connect keeps a clean api.bamf.ai contract, stable resource naming, and clear product-facing endpoints.
- 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.