canonical: https://jentic.com/apis/gallabox.com/gallabox

# Gallabox API

Jentic publishes the only available OpenAPI specification for Gallabox API, keeping it validated and agent-ready. The Gallabox API exposes the platform's WhatsApp Business automation surface, covering outbound message sending, template messaging, contact management, and conversation operations so businesses can drive WhatsApp interactions from internal CRMs and chatbots. Authentication uses an API key issued from the Gallabox workspace, and outbound calls go through server.gallabox.com. The API is targeted at Indian and APAC commerce, support, and lead-conversion teams that already use WhatsApp as a primary channel and want to automate template messaging, opt-in handling, and contact sync from outside the Gallabox dashboard.

## For AI agents

Send WhatsApp Business messages, run template campaigns, manage contacts, and orchestrate conversations through Gallabox using API-key authenticated calls.

## Scope

Does not handle SMS, voice calls, or email - use for WhatsApp Business messaging, contacts, and conversations through Gallabox only.

## Capabilities

- Send WhatsApp template messages to opted-in contacts through the Gallabox sender endpoint
- Create and update contacts inside the Gallabox workspace for downstream messaging
- Trigger session-based WhatsApp replies during the 24-hour customer-service window
- List and update conversations to mark threads as read or assigned to an agent
- Apply tags to contacts so segmentation drives template selection automatically
- Subscribe webhooks to receive inbound WhatsApp messages and delivery status updates

## Use cases

### Order Status WhatsApp Notifications

Trigger WhatsApp template messages from an e-commerce backend whenever an order ships by calling the Gallabox send-template operation with the customer's number and the dispatch template id. The flow keeps customers informed on their preferred channel without manual outreach.

Example prompt: Call the Gallabox send-template endpoint with the customer's phone number, the dispatch template id, and the order tracking variables.

### Lead Capture and Tagging

When a lead form is submitted on a website, push the contact into Gallabox via the contacts endpoint and tag the record so the next campaign run targets only the new leads. Tags drive template selection and keep segmentation consistent with marketing's plan.

Example prompt: Create a contact for the lead with their phone number and apply the 'new-lead' tag using the Gallabox contact and tag endpoints.

### Inbound Customer Service Reply

Receive inbound WhatsApp messages via a Gallabox webhook and call the session-message endpoint to reply within the 24-hour service window without using a paid template. This keeps cost down for back-and-forth support conversations.

Example prompt: Listen to the inbound webhook, then call the Gallabox session-message endpoint with the visitor's phone and the agent's reply text.

### Agent-Driven WhatsApp Operations via Jentic

A customer-success agent receives a request like 'send the renewal reminder template to all customers expiring this week' and uses Jentic to discover the Gallabox send-template operation, load its parameters, and execute it with the workspace API key. Jentic isolates the key so the agent never holds it directly.

Example prompt: Search Jentic for 'send a gallabox whatsapp template', load the send-template operation, and execute it for each phone number in the renewal list.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/messages` | Send a WhatsApp template or session message |
| GET | `/contacts` | List Gallabox contacts |
| POST | `/contacts` | Create a new contact |
| GET | `/conversations` | List conversations |
| POST | `/webhooks` | Subscribe to inbound and delivery events |

## Key resources

- **Messages** — Send template and session-based WhatsApp messages through Gallabox.
- **Contacts** — Create, update, and tag contacts in the Gallabox workspace.
- **Conversations** — List and update WhatsApp conversation threads.
- **Webhooks** — Receive inbound message and delivery-status events.

## Why Jentic

- **Setup:** Wiring the Gallabox API by hand means setting up its API-key auth against server.gallabox.com and coordinating WhatsApp message, contact, conversation, and webhook calls yourself. Through Jentic you install once, import the Gallabox API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Gallabox carries the message and contact details in the request body rather than a URL path resource, so scope this by operation: limit the agent to the operations it needs, such as sending a message or reading contacts, and leave writes like creating webhooks out of the allowed set. Every operation the agent can run is one you chose to include.
- **Credential handling:** Your Gallabox API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'send a WhatsApp message' or 'list Gallabox contacts', and Jentic returns the matching Gallabox API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Twilio Messaging API** — Global messaging API spanning WhatsApp, SMS, and MMS, broader than Gallabox's WhatsApp focus.
- **Facebook Graph API** — Meta's Graph API surface that includes the WhatsApp Business Cloud endpoints used directly without a BSP layer.

## FAQ

### Why is there no official OpenAPI spec for Gallabox API?

Gallabox does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Gallabox API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Gallabox API use?

Gallabox issues a workspace API key that callers send on every request to server.gallabox.com. Through Jentic, the key is stored encrypted in the vault and injected at execution so the raw key never enters the agent's prompt.

### Can I send WhatsApp template messages with the Gallabox API?

Yes. Post to the messages endpoint with the recipient phone, the template id, and any parameter variables; Gallabox handles delivery to Meta's WhatsApp Business platform and returns a status that can be tracked via webhook.

### What are the rate limits for the Gallabox API?

Limits depend on the Gallabox plan and on Meta's WhatsApp tier the workspace is approved for; Gallabox does not embed numeric quotas in published documentation. Watch for HTTP 429 responses and consult Gallabox support for your plan's specific ceilings.

### How do I send a WhatsApp template through Jentic?

Run a Jentic search for 'send a gallabox whatsapp template', load the messages endpoint, and execute it with the recipient phone, template id, and variables. Get started with Jentic One, the self-hosted execution layer.

### Can I limit what my agent is allowed to do with the Gallabox API?

Yes. Because your Jentic One instance is self-hosted, your own rules decide which Gallabox operations and credentials the agent may use. Since Gallabox passes message and contact details in the request body rather than a URL path, you scope access per operation: allow only what the agent needs, such as sending a WhatsApp template message or listing contacts, and leave writes like creating contacts or subscribing webhooks out of the allowed set. Every operation the agent can call is one you chose to include.