# SambungAPI: connect your bots and agents to the channels and tools they work with

SambungAPI is the one connection for the tools your team's bots use: WhatsApp, Gmail, Google Calendar, and more, with a simple API for developers.

[Create account](/signup) or [Sign in](/login). Free to start.

**Channels** are where your bots talk to people: WhatsApp today, with Messenger, Instagram, Teams, and Slack coming later. **Tools** are what your bots can read, write, and act on: Google today, with GitHub, Outlook, OneDrive, Notion, Linear, and Jira coming later, and more arriving as the catalog grows.

## For businesses

Your team answers the people who message your business on WhatsApp, from one place: Chats, Contacts and message templates. You can connect your WhatsApp Business Account yourself, with Meta's guided signup. If you have no developer, [contact us](/contact).

A business with no developer starts with [SambungAPI for businesses](/business): what your team can do without a developer, what needs one today, and what it costs.

## How your app connects a tool

Your app chooses the project and the tool. Your user then approves the access on the provider's own page.

1. Choose a project and tool
2. Open the provider's authorization page
3. Return with a connected account and run a live action

Your user's password at the provider never reaches SambungAPI. SambungAPI encrypts and stores the tokens that the provider issues for the connected account.

Step 3 in your code: one request runs the action through your user's account. [The SambungAPI API](/docs/api#execute-a-tool) shows that request.

## Documentation for developers

Read these before you build. Each line says when the page is the one you want.

A project key is the credential your software uses to run tools for one project. The API guide says where to mint one.

- [The SambungAPI API](/docs/api): Make the first call: where to mint a key, the tool-execute path and its envelope, and the WhatsApp gateway send.
- [Connect an MCP client](/docs/mcp): Give an agent the tools through MCP: the endpoint, the project key, the application user, and the connect step.
- [The tool catalog](/docs/tools): Plan a call before you sign up: the toolkits SambungAPI offers, and the arguments each tool takes.
- [Coming from the Composio SDK](/docs/composio): Why the Composio SDK's tools.execute does not reach this server, and the plain HTTP request to send instead.
- [Moving to SambungAPI from another WhatsApp provider](/docs/migrate-whatsapp): Already on another WhatsApp provider: connect the same number here, rebuild on SambungAPI, and then remove your source provider.
- [Your first WhatsApp message](/docs/try-whatsapp): Send a first WhatsApp message on Meta's test account, before a production WhatsApp Business Account exists.
- [What SambungAPI owns](/docs/why): Weighing this against calling Meta's WhatsApp Cloud API yourself: the machinery around a send, and the boundary Meta keeps.

An agent starts with [/llms.txt](/llms.txt): when to use SambungAPI, and which address to read first. The [Documentation](/docs) index lists every machine-readable description of the API.

Metatech ID (PT Trifidia Cipta Korpora) builds and operates SambungAPI.

[Docs](/docs) · [For businesses](/business) · [About](/about) · [Contact](/contact) · [Privacy](/privacy) · [Terms](/terms)