2Chat WhatsApp API

Name: 2Chat WhatsApp API
Brand: 2Chat WhatsApp API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsChat MessagingapiKey5 EndpointsREST

For Agents

Send WhatsApp text, image, and document messages from a connected 2Chat number, list connected numbers, and verify whether a phone number is on WhatsApp.

Install Jentic One Beta

Connect the 2Chat WhatsApp API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the 2Chat WhatsApp API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with 2Chat WhatsApp API.

Send WhatsApp text messages from a connected number to any recipient in E.164 format

Deliver image messages with an optional caption by referencing a public image URL

Send document or file messages with a custom filename and caption to a WhatsApp recipient

GET STARTED

Start building with 2Chat WhatsApp API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use 2Chat WhatsApp API for, with concrete tasks.

★ WhatsApp Order Confirmations

Send transactional WhatsApp messages such as order confirmations and shipping updates from a 2Chat-connected business number. The text endpoint accepts a recipient number in E.164 format and a message body, and returns a message UUID and status for delivery tracking. This avoids the WhatsApp Business Platform onboarding by reusing an already-connected number.

Send a WhatsApp text message to +14155551234 saying 'Your order #1042 has shipped — tracking: 1ZA999' from the connected 2Chat number 14155556789 and capture the returned message UUID.

Document Delivery Over WhatsApp

Deliver invoices, receipts, contracts, or boarding passes as WhatsApp document messages by passing a public URL, filename, and optional caption. The 2Chat document endpoint forwards the file to the recipient's WhatsApp client without requiring local upload, which keeps integration light for back-office systems generating PDFs on the fly.

Send the PDF at https://example.com/invoice-1042.pdf as a WhatsApp document with filename 'invoice-1042.pdf' and caption 'Your June invoice' to recipient +442071234567 using the connected number 14155556789.

WhatsApp Number Validation

Before launching a WhatsApp campaign or 1:1 outreach, verify that the destination number is actually registered on WhatsApp. The check-number endpoint returns a boolean indicating WhatsApp registration status, letting applications skip non-WhatsApp numbers and reduce delivery failures.

For a list of 50 phone numbers, call the check-number endpoint using connected number 14155556789 and return only the subset that are registered on WhatsApp.

Agent-Driven WhatsApp Outreach

Allow an AI agent to handle WhatsApp messaging end-to-end through Jentic: discover the 2Chat send-text operation by intent, load the input schema, supply recipient and message body, and execute. Credentials stay isolated in Jentic's vault — the agent never sees the raw 2Chat API key.

Through Jentic, search for 'send a whatsapp message', load the 2Chat sendTextMessage schema, and dispatch a personalised reminder to each recipient in a contact list.

Key Endpoints

5 endpoints — jentic publishes the only available openapi specification for 2chat whatsapp api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/api/v1/whatsapp/numbers/{phoneNumber}/messages/text

Send a WhatsApp text message

POST

/api/v1/whatsapp/numbers/{phoneNumber}/messages/image

Send a WhatsApp image with optional caption

POST

/api/v1/whatsapp/numbers/{phoneNumber}/messages/document

Send a WhatsApp document or file

GET

/api/v1/whatsapp/numbers

List connected WhatsApp numbers

GET

/api/v1/whatsapp/numbers/{phoneNumber}/check-number/{targetNumber}

Check whether a number is on WhatsApp

POST

/api/v1/whatsapp/numbers/{phoneNumber}/messages/text

Send a WhatsApp text message

POST

/api/v1/whatsapp/numbers/{phoneNumber}/messages/image

Send a WhatsApp image with optional caption

POST

/api/v1/whatsapp/numbers/{phoneNumber}/messages/document

Send a WhatsApp document or file

GET

/api/v1/whatsapp/numbers

List connected WhatsApp numbers

GET

/api/v1/whatsapp/numbers/{phoneNumber}/check-number/{targetNumber}

Check whether a number is on WhatsApp

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The 2Chat X-User-API-Key is stored encrypted in the Jentic vault. Agents call sendTextMessage and other operations through Jentic, which injects the header at execution — the raw key never enters the agent's context.

Intent-based discovery

Agents search Jentic by intent (e.g., 'send a whatsapp message') and Jentic returns the matching 2Chat operation along with its input schema, so the agent calls the correct endpoint without reading the 2Chat docs.

Time to first call

Direct 2Chat integration: roughly half a day to handle auth, payload shaping, and error mapping. Through Jentic: under 30 minutes — search, load, execute.

FAQs

Specific to using 2Chat WhatsApp API through Jentic.

Why is there no official OpenAPI spec for 2Chat WhatsApp API?

2Chat does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call 2Chat WhatsApp API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the 2Chat WhatsApp API use?

It uses an API key passed in the X-User-API-Key request header. Through Jentic, the key is stored encrypted in the vault and injected at execution time, so agents never see the raw secret in their context.

Can I send WhatsApp images and documents through the 2Chat API?

Yes. POST /api/v1/whatsapp/numbers/{phoneNumber}/messages/image accepts an image URL and optional caption, and POST /api/v1/whatsapp/numbers/{phoneNumber}/messages/document accepts a file URL plus filename and caption. Both return a message UUID for tracking.

How do I check if a phone number is on WhatsApp before messaging?

Call GET /api/v1/whatsapp/numbers/{phoneNumber}/check-number/{targetNumber} with one of your connected numbers and the target number in E.164 format (no leading +). The response includes is_whatsapp_user, which you can use to filter recipients.

How do I send a WhatsApp message with the 2Chat API through Jentic?

Run pip install jentic, then use the search-load-execute flow: search for 'send a whatsapp message', load the sendTextMessage operation, supply your connected phoneNumber, to_number, and text, and execute. Sign up at https://app.jentic.com/sign-up to get an agent API key for execution.

What number format does 2Chat expect for WhatsApp recipients?

Phone numbers must be in E.164 format without the leading + sign. For example, the US number +1 415 555 1234 is passed as 14155551234 in both the path parameter and the to_number body field.

2Chat WhatsApp API

Connect the 2Chat WhatsApp API to your agent

Capabilities

Start building with 2Chat WhatsApp API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs