AI Number API

Name: AI Number API API
Brand: AI Number API
Availability: InStock

★ Only Publicly Available SpecCommunicationsChat MessagingapiKey20 EndpointsREST

For Agents

Send WhatsApp messages, manage contacts and tags, and orchestrate customer-care conversations through the AI Number platform.

Quickstart

Get started with AI Number API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"send a whatsapp template message"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with AI Number API API.

Send approved WhatsApp template messages to contacts via /conversations/messages/templates/send

Send free-form customer-care replies inside the 24-hour service window

Create, update, and tag contacts to drive segmentation and routing rules

Define custom contact fields to capture business-specific attributes

GET STARTED

Start building with AI Number API API

Explore with Jentic

View OpenAPI Spec

Jentic publishes the only available OpenAPI specification for AI Number API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for AI Number API, keeping it validated and agent-ready. AI Number, formerly Sendbee, is a WhatsApp Business messaging platform for managing teams, contacts, and conversations across customer support and outbound campaigns. The API exposes 20 endpoints covering team rosters, contact records with tags and custom fields, conversation threads, customer-care messages, and approved template messages. Authentication uses paired authToken and X-API-Key headers.

Use Cases

Patterns agents use AI Number API API for, with concrete tasks.

★ WhatsApp Customer Support Automation

Operate a WhatsApp-first support inbox where agents and bots handle inbound conversations through the same API. List open threads with /conversations, pull full transcripts via /conversations/messages, then reply with /conversations/messages/send while the customer-care window is open. Outside the window, fall back to approved templates.

List the 5 oldest unread conversations, summarise each with their last 10 messages, and post a customer-care reply to the first one acknowledging receipt

Outbound WhatsApp Campaigns with Templates

Send approved WhatsApp template messages to a tagged contact list — for order confirmations, appointment reminders, or re-engagement. The template send endpoint accepts variable substitutions per recipient, and tag-based contact filtering keeps the audience tight.

Find all contacts tagged 'reminder_due', then send the appointment_reminder template to each with their first name as the variable

Contact Enrichment and Segmentation

Build a tagged, custom-field-rich contact database that doubles as a CRM lite for messaging. Create custom fields with /contacts/fields, tag contacts based on lifecycle stage, and update records as conversations evolve so subsequent messages can be targeted by attribute.

Create a custom field called 'plan_tier' of type string, then update contact c_777 setting plan_tier=premium and add the tag 'vip'

AI Agent WhatsApp Operator

An agent triages an inbound WhatsApp conversation through Jentic — fetching the thread, drafting a reply, and posting it back to the customer without operator handoff. Jentic handles the auth pairing (authToken plus X-API-Key) so the agent only sees scoped operations.

Search Jentic for 'send whatsapp customer care message', load the schema for /conversations/messages/send, and post a reply to conversation conv_123 saying 'Your order has shipped'

Key Endpoints

20 endpoints — jentic publishes the only available openapi specification for ai number api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/conversations/messages/send

Send a customer-care WhatsApp message

POST

/conversations/messages/templates/send

Send an approved WhatsApp template message

GET

/conversations

List conversation threads

GET

/conversations/messages

List messages within a conversation

POST

/contacts/subscribe

Create a new contact

GET

/contacts

List contacts

POST

/contacts/tags

Create a contact tag

POST

/conversations/messages/send

Send a customer-care WhatsApp message

POST

/conversations/messages/templates/send

Send an approved WhatsApp template message

GET

/conversations

List conversation threads

GET

/conversations/messages

List messages within a conversation

POST

/contacts/subscribe

Create a new contact

Why though Jentic?

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

Credential isolation

AI Number requires both an authToken and an X-API-Key header. Jentic stores both encrypted in the vault and injects them at call time, so agents never handle the raw secrets.

Intent-based discovery

Agents search Jentic by intent (e.g. 'send a whatsapp template') and receive the matching AI Number operation with its input schema, removing the need to browse Sendbee documentation.

Time to first call

Direct AI Number integration: 1-3 days for paired auth, template approval handling, and conversation pagination. Through Jentic: under 1 hour.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Gupshup API

Multi-channel conversational messaging including WhatsApp Business, RCS, and SMS

Choose Gupshup when the agent needs RCS or SMS alongside WhatsApp from a single platform

Alternative

Twilio Messaging API

WhatsApp, SMS, and MMS messaging with global reach and detailed delivery telemetry

Choose Twilio when the agent already uses Twilio for voice or SMS and wants one auth scheme

Complementary

HubSpot CRM Contacts

Sync AI Number contacts with a primary CRM for unified customer records

Use HubSpot alongside AI Number to keep messaging history aligned with the contact record of truth

FAQs

Specific to using AI Number API API through Jentic.

Why is there no official OpenAPI spec for AI Number API?

AI Number does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AI Number 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 AI Number API use?

AI Number requires two paired headers: authToken and X-API-Key. Both are stored encrypted in the Jentic vault, so agents calling AI Number through Jentic receive scoped access without ever seeing the raw credentials.

Can I send a WhatsApp template message with the AI Number API?

Yes. POST /conversations/messages/templates/send dispatches an approved template to a contact, with variable substitutions for personalised content. Use GET /conversations/messages/templates first to confirm which templates are approved.

What are the rate limits for the AI Number API?

Rate limits are not declared in the spec and are governed by the underlying WhatsApp Business platform. For high-throughput sending, batch by contact tag and respect WhatsApp's per-template messaging quality rating.

How do I send a customer-care reply with the AI Number API through Jentic?

Run pip install jentic, search Jentic for 'send whatsapp customer care message', load the schema for POST /conversations/messages/send, then execute with the conversation ID and message body. Jentic injects both the authToken and X-API-Key headers.

Can I tag and segment contacts through the AI Number API?

Yes. Create tags with POST /contacts/tags and custom fields with POST /contacts/fields, then PUT /contacts to update individual records. Tags and fields can both be used as filters when targeting outbound campaigns.