Open a new ticket for whatsapp
curl --request POST \
--url https://api.vambe.me/api/public/ticket/open/whatsapp/{phoneId} \
--header 'Content-Type: application/json' \
--header 'x-api-key: <x-api-key>' \
--data '
{
"to_phone_number": 2,
"stage_id": "<string>"
}
'const options = {
method: 'POST',
headers: {'x-api-key': '<x-api-key>', 'Content-Type': 'application/json'},
body: JSON.stringify({to_phone_number: 2, stage_id: '<string>'})
};
fetch('https://api.vambe.me/api/public/ticket/open/whatsapp/{phoneId}', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.vambe.me/api/public/ticket/open/whatsapp/{phoneId}"
payload = {
"to_phone_number": 2,
"stage_id": "<string>"
}
headers = {
"x-api-key": "<x-api-key>",
"Content-Type": "application/json"
}
response = requests.post(url, json=payload, headers=headers)
print(response.text)Tickets
Open a new ticket for whatsapp
POST
/
api
/
public
/
ticket
/
open
/
whatsapp
/
{phoneId}
Open a new ticket for whatsapp
curl --request POST \
--url https://api.vambe.me/api/public/ticket/open/whatsapp/{phoneId} \
--header 'Content-Type: application/json' \
--header 'x-api-key: <x-api-key>' \
--data '
{
"to_phone_number": 2,
"stage_id": "<string>"
}
'const options = {
method: 'POST',
headers: {'x-api-key': '<x-api-key>', 'Content-Type': 'application/json'},
body: JSON.stringify({to_phone_number: 2, stage_id: '<string>'})
};
fetch('https://api.vambe.me/api/public/ticket/open/whatsapp/{phoneId}', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.vambe.me/api/public/ticket/open/whatsapp/{phoneId}"
payload = {
"to_phone_number": 2,
"stage_id": "<string>"
}
headers = {
"x-api-key": "<x-api-key>",
"Content-Type": "application/json"
}
response = requests.post(url, json=payload, headers=headers)
print(response.text)Overview
Create a new support ticket for a WhatsApp Business API contact. This endpoint initializes a conversation in a specific pipeline stage, optionally sends an initial message, and allows you to set custom metadata for both the contact and ticket. This endpoint is specifically for WhatsApp Business API connections (not WhatsApp Web/QR). Use this when you have an official WhatsApp Business API integration.Use Cases
- Form-triggered Tickets: Create a ticket when a user submits a contact form
- E-commerce Integration: Open tickets for new orders or delivery issues
- Onboarding Workflows: Start onboarding tickets for new customers
- Support Escalation: Programmatically create tickets from other systems
- Event-based Tickets: Create tickets based on user behavior or triggers
- CRM Synchronization: Sync customer issues from external CRM to Vambe
Authentication
This endpoint requires authentication using an API key. Include your API key in the request header:x-api-key: your_api_key_here
Path Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
phoneId | number/string | Yes | Your WhatsApp Business API phone ID (numeric) |
WhatsApp Business API: The
phoneId must be a numeric ID from your
WhatsApp Business API configuration. This is different from WhatsApp Web (QR)
which uses string identifiers.Request Body
| Field | Type | Required | Description |
|---|---|---|---|
to_phone_number | string | Yes | Contactโs WhatsApp phone number (with country code) |
stage_id | string | Yes | UUID of the pipeline stage where the ticket should start |
contact_name | string | No | Full name of the contact |
email | string | No | Contactโs email address (must be valid email format) |
contact_metadata | object | No | Custom key-value pairs for contact-level data |
ticket_metadata | object | No | Custom key-value pairs for ticket-level data |
integration_data | object | No | Integration-specific data (e.g., external system IDs) |
message | object | No | Optional initial message to send when creating the ticket |
Message Object
When providing an initial message, use this structure:| Field | Type | Required | Description |
|---|---|---|---|
content | string | No | Text content of the message to send |
templateId | string | No | ID of a template to use (if using smart templates) |
ai_generated | boolean | Yes | Whether the message is AI-generated (true) or manual |
Response Structure
The endpoint returns a success response with the created contact information:| Field | Type | Description |
|---|---|---|
aiContactId | string (UUID) | Unique identifier of the created or existing contact |
status | string | Status of the operation (always โokโ) |
Example Request
curl --request POST \
'https://api.vambe.me/api/public/ticket/open/whatsapp/123456789' \
--header 'Content-Type: application/json' \
--header 'x-api-key: your_api_key_here' \
--data-raw '{
"to_phone_number": "+56912345678",
"stage_id": "550e8400-e29b-41d4-a716-446655440000",
"contact_name": "Maria Rodriguez",
"email": "maria.rodriguez@example.com",
"contact_metadata": {
"company": "Acme Corp",
"plan": "Premium",
"source": "website_form"
},
"ticket_metadata": {
"issue_type": "billing",
"priority": "high",
"order_id": "ORD-12345"
},
"message": {
"content": "Hola Maria! Hemos recibido tu consulta sobre facturaciรณn. ยฟEn quรฉ podemos ayudarte?",
"ai_generated": false
}
}'
Example Response
{
"aiContactId": "df980fc8-b6db-4820-bf22-2969482d106d",
"status": "ok"
}
Common Use Cases
1. Create Ticket from Contact Form
const createTicketFromForm = async (formData) => {
const response = await fetch(
'https://api.vambe.me/api/public/ticket/open/whatsapp/123456789',
{
method: 'POST',
headers: {
'Content-Type': 'application/json',
'x-api-key': 'your_api_key_here',
},
body: JSON.stringify({
to_phone_number: formData.phone,
stage_id: 'your_initial_stage_id',
contact_name: formData.name,
email: formData.email,
contact_metadata: {
form_source: 'contact_page',
submission_date: new Date().toISOString(),
},
ticket_metadata: {
subject: formData.subject,
message: formData.message,
},
message: {
content: `Hola ${formData.name}! Hemos recibido tu mensaje y te responderemos pronto.`,
ai_generated: false,
},
}),
},
);
const result = await response.json();
console.log('Ticket created for contact:', result.aiContactId);
return result;
};
2. E-commerce Order Ticket
const createOrderTicket = async (order) => {
const response = await fetch(
'https://api.vambe.me/api/public/ticket/open/whatsapp/123456789',
{
method: 'POST',
headers: {
'Content-Type': 'application/json',
'x-api-key': 'your_api_key_here',
},
body: JSON.stringify({
to_phone_number: order.customerPhone,
stage_id: 'your_orders_stage_id',
contact_name: order.customerName,
email: order.customerEmail,
contact_metadata: {
customer_since: order.accountCreatedDate,
lifetime_value: order.lifetimeValue.toString(),
},
ticket_metadata: {
order_id: order.id,
order_total: order.total.toString(),
items: order.items.length.toString(),
payment_method: order.paymentMethod,
},
integration_data: {
shopify_order_id: order.shopifyId,
tracking_number: order.trackingNumber,
},
message: {
content: `ยกHola ${order.customerName}! Tu pedido #${order.id} ha sido confirmado y serรก enviado pronto. Total: $${order.total}`,
ai_generated: false,
},
}),
},
);
return await response.json();
};
3. Create Ticket Without Initial Message
// Let the AI assistant handle the first message based on pipeline configuration
const createSilentTicket = async (phone, stageId) => {
const response = await fetch(
'https://api.vambe.me/api/public/ticket/open/whatsapp/123456789',
{
method: 'POST',
headers: {
'Content-Type': 'application/json',
'x-api-key': 'your_api_key_here',
},
body: JSON.stringify({
to_phone_number: phone,
stage_id: stageId,
// No message object - AI will handle first contact
}),
},
);
return await response.json();
};
4. Using Smart Templates
const createTicketWithTemplate = async (contact, templateId) => {
const response = await fetch(
'https://api.vambe.me/api/public/ticket/open/whatsapp/123456789',
{
method: 'POST',
headers: {
'Content-Type': 'application/json',
'x-api-key': 'your_api_key_here',
},
body: JSON.stringify({
to_phone_number: contact.phone,
stage_id: 'your_stage_id',
contact_name: contact.name,
message: {
templateId: templateId,
content: contact.name, // Template variable
ai_generated: false,
},
}),
},
);
return await response.json();
};
Phone ID Requirements
The
phoneId in the path must be a numeric ID from your WhatsApp Business
API configuration. This is NOT the phone number itself.- โ
Correct:
123456789(numeric phone ID from WhatsApp Business API) - โ Incorrect:
"+56912345678"(this is the customerโs phone number, not your phone ID) - โ Incorrect:
"my-phone-id"(string identifier - use web-whatsapp endpoint instead)
- Check your WhatsApp Business API configuration
- Look in your Vambe dashboard under WhatsApp channels
- The phone ID is a numeric value assigned by WhatsApp
Phone Number Format
Theto_phone_number field accepts phone numbers in various formats:
- With country code:
"+56912345678"(recommended) - String format:
"56912345678" - Number format:
56912345678
Metadata Best Practices
Contact Metadata
Store information about the person:- Company name
- Industry
- Customer tier/plan
- Account creation date
- Language preference
- Time zone
Ticket Metadata
Store information about this specific ticket:- Issue type/category
- Priority level
- Related order/transaction IDs
- Urgency
- Source (web, mobile, API, etc.)
- Custom fields specific to your workflow
Error Responses
| Status Code | Description |
|---|---|
| 400 | Bad Request - Invalid phone number or stage ID |
| 401 | Unauthorized - Invalid or missing API key |
| 404 | Not Found - Phone ID doesnโt exist or is not numeric |
| 500 | Internal Server Error - Something went wrong |
Important Notes
- Phone ID Must Be Numeric: The
phoneIdparameter must be a number, not a string identifier - WhatsApp Business API Only: This endpoint is for official WhatsApp Business API connections
- For WhatsApp Web: Use
POST /api/public/ticket/open/web-whatsapp/{phoneId}instead - Stage ID: Make sure the
stage_idexists in your pipelines - use GET /api/public/pipeline to get valid stage IDs - Duplicate Contacts: If a contact with the same phone number already exists, the ticket will be created for that existing contact
- Metadata Flexibility: Both
contact_metadataandticket_metadataaccept any key-value pairs as objects - AI Processing: When you donโt provide a message, the AI assistant will automatically engage based on your pipeline configuration
- Message vs Template: You can provide either plain
contentor use atemplateIdwith variables
What Happens After Creation
- Phone ID Validation: System verifies the phone ID is numeric and exists
- Contact Creation/Update: The system finds or creates a contact with the provided phone number
- Metadata Processing: Contact and ticket metadata are processed and stored
- Stage Assignment: The ticket is placed in the specified pipeline stage
- Message Sending (if provided):
- If
message.contentis provided withouttemplateId: Sends a plain text message via WhatsApp Business API - If
message.templateIdis provided: Sends a WhatsApp approved template with variables - If no message: AI assistant takes over based on pipeline configuration
- If
- Contact ID Return: You receive the
aiContactIdto track this contact for future operations
WhatsApp Business API vs WhatsApp Web
| Feature | WhatsApp Business API (This) | WhatsApp Web (QR) |
|---|---|---|
| Endpoint | /api/public/ticket/open/whatsapp/ | /api/public/ticket/open/web-whatsapp/ |
| Phone ID Format | Numeric (e.g., 123456789) | String (e.g., "phone_abc123") |
| Connection Type | Official API from Meta | QR code connection |
| Message Types | Templates and plain text | Plain text only |
| Reliability | Higher (official API) | Depends on QR connection |
| Scalability | Better for high volume | Limited by QR session |
Related Endpoints
- GET /api/public/pipeline - Get available pipeline stages
- GET /api/public/contact//info - Get ticket and contact info
- POST /api/public/contact//update-metadata - Update contact metadata later
- POST /api/public/ticket/close/contact/ - Close an active ticket
- POST /api/public/ticket/open/web-whatsapp/ - WhatsApp Web version
Complete Workflow Example
// Complete workflow: Search contact, create ticket if needed
const createOrUpdateTicket = async (customerData) => {
// 1. Search if contact already exists
const searchResponse = await fetch(
`https://api.vambe.me/api/public/contacts/search?phone=${encodeURIComponent(customerData.phone)}`,
{
headers: {
'x-api-key': 'your_api_key_here',
},
},
);
const existingContacts = await searchResponse.json();
if (existingContacts.length > 0) {
console.log('Contact exists, creating new ticket');
// Contact exists - just create new ticket with updated metadata
} else {
console.log('New contact - creating first ticket');
}
// 2. Create ticket (works for both new and existing contacts)
const ticketResponse = await fetch(
'https://api.vambe.me/api/public/ticket/open/whatsapp/123456789',
{
method: 'POST',
headers: {
'Content-Type': 'application/json',
'x-api-key': 'your_api_key_here',
},
body: JSON.stringify({
to_phone_number: customerData.phone,
stage_id: 'your_stage_id',
contact_name: customerData.name,
email: customerData.email,
contact_metadata: {
company: customerData.company,
updated_at: new Date().toISOString(),
},
ticket_metadata: {
ticket_type: customerData.inquiryType,
source: 'api',
},
message: {
content: `Hola ${customerData.name}! Gracias por contactarnos.`,
ai_generated: false,
},
}),
},
);
const result = await ticketResponse.json();
console.log('Ticket created:', result.aiContactId);
return result;
};
Headers
API key needed to authorize the request
Path Parameters
Body
application/json
Required range:
x >= 1Pattern:
^(?!\.)(?!.*\.\.)([A-Za-z0-9_'+\-\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\-]*\.)+[A-Za-z]{2,}$Show child attributes
Show child attributes
Response
200
Ticket created successfully
Was this page helpful?
