ABC Salesbot Public API: Overview and Quick Start

ABC Salesbot has a documented public REST API. Anything with an internet connection can push leads in, read conversations out, send messages, and react to events in real time. This page gives you the map; the full interactive reference lives in the developer docs.

• Developer guide: app.abcsalesbot.com/docs/api
• Interactive reference (Swagger): api.abcsalesbot.com/docs/api

Authentication

Every request uses a Bearer token:

• Get your API key from the Integration section of your dashboard
• Send it on every request as the header Authorization: Bearer YOUR_API_KEY
• Base URL: https://api.abcsalesbot.com/v1

What the API can do

• Create leads from anywhere: POST /v1/webhooks/leads accepts new leads from your website forms, funnels, CRM, or any custom system, no Zapier required.
• Read a lead's conversation: GET /v1/leads/{leadID}/conversations returns the full message history between your AI Employee and that lead.
• Send a message programmatically: POST /v1/leads/{leadID}/conversations/reply lets your own system reply to a lead through ABC Salesbot.
• List your connected channels: GET /v1/messaging-channel-connections shows every WhatsApp, LINE, Facebook, Instagram, and Telegram connection on your account.
• Download attachments: GET /v1/attachments/{id}/download retrieves files customers sent in chat.
• Verify your key: GET /v1/companies/me returns the company the key belongs to, useful as a connection test.

Webhook subscriptions (events out)

Subscriptions push events from ABC Salesbot to your system the moment they happen:

• GET /v1/webhook-subscriptions/events lists every event trigger you can subscribe to
• Create, update, and delete subscriptions via POST, PUT, and DELETE /v1/webhook-subscriptions
• Each subscription has a signing secret so you can verify payloads; rotate it any time with POST /v1/webhook-subscriptions/{subscriptionId}/regenerate-secret

For a walkthrough of webhook payloads and use cases, see the Outgoing Webhooks guide.

Rate limits

There are currently no hard rate limits under fair use. Standard HTTP status codes (400, 401, 403, 404, 429) signal errors, so build normal retry handling.