Skip to main content
POST
/
v1
/
bots
/
{botId}
/
messages
curl --request POST \
  --url https://api.jelou.ai/v1/bots/BOT_ID/messages \
  --header 'Authorization: Basic <Base64Encoded clientId:clientSecret>' \
  --header 'Content-Type: application/json' \
  --data '{
    "type": "flow",
    "title": "Hola",
    "text": "Completa este flujo para comenzar",
    "caption": "Jelou",
    "userId": "USER_ID",
    "parameters": {
      "flow_id": "FLOW_ID",
      "flow_cta": "Iniciar Flujo",
      "flow_name": "Flujo de Bienvenida",
      "flow_action_payload": {
        "screen": "RECOMMEND"
      },
      "mode": "draft",
      "flow_action": "navigate",
      "flow_message_version": "3"
    }
  }'

{
  "success": true,
  "messageId": "msg_123456789"
}
curl --request POST \
  --url https://api.jelou.ai/v1/bots/BOT_ID/messages \
  --header 'Authorization: Basic <Base64Encoded clientId:clientSecret>' \
  --header 'Content-Type: application/json' \
  --data '{
    "type": "flow",
    "title": "Hola",
    "text": "Completa este flujo para comenzar",
    "caption": "Jelou",
    "userId": "USER_ID",
    "parameters": {
      "flow_id": "FLOW_ID",
      "flow_cta": "Iniciar Flujo",
      "flow_name": "Flujo de Bienvenida",
      "flow_action_payload": {
        "screen": "RECOMMEND"
      },
      "mode": "draft",
      "flow_action": "navigate",
      "flow_message_version": "3"
    }
  }'

​
Mejores Prácticas

Flujos Complejos: Usa botones de flujo para interacciones complejas de múltiples pasos que requieren entradas de formulario, selecciones o experiencias guiadas. Los flujos proporcionan una experiencia nativa de WhatsApp sin salir del chat.

​
Casos de Uso

  • Formularios de registro o encuestas
  • Procesos de compra multi-paso
  • Configuraciones guiadas
  • Experiencias interactivas complejas

Authorizations

​
Authorization
string
header
required

Basic authentication using Base64 encoded clientId:clientSecret

Path Parameters

​
botId
string
required

The unique identifier of the bot

Body

application/json

Message payload. The structure varies based on the message type.

​
type
enum<string>
required

Type of message to send

Available options:
text
Example:

"text"

​
userId
string
required

Unique identifier of the user receiving the message

Example:

"USER_ID"

​
text
string
required

Text content of the message

Example:

"Hello, this is a text message"

​
botId
string

Unique identifier of the bot sending the message

Example:

"BOT_ID"

Response

Message sent successfully

​
success
boolean
Example:

true

​
messageId
string
Example:

"msg_123456789"