Sending messages

One endpoint, all three channels:

curl -X POST https://api.neike.dev/api/outbound/send \
  -H "x-neike-api-key: whk_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "channelId": "nk_dvzobn7m4h4y",
    "to": "5491112345678",
    "type": "text",
    "content": { "text": "Yes, we do." }
  }'

{ "ok": true, "jobId": "outbound_nk_dvzobn7m4h4y_1712345678901" }

202 means queued, not delivered. Delivery arrives on your webhook as a status update.

Addressing

to is the counterpart’s identifier for that platform:

Channel	`to`
WhatsApp	Phone number in E.164 without `+` — `5491112345678`
Instagram	The IGSID you received in the inbound message
Messenger	The PSID you received in the inbound message

For Instagram and Messenger you cannot invent a recipient: you can only reply to someone who wrote to you first, using the id from their message.

Content by type

content changes shape with type:

{ "type": "text", "content": { "text": "Hello" } }

{
  "type": "image",
  "content": { "image": { "link": "https://…/photo.jpg", "caption": "Optional" } }
}

{
  "type": "document",
  "content": { "document": { "link": "https://…/invoice.pdf", "filename": "invoice.pdf" } }
}

Media is sent by link: the URL has to be publicly reachable so Meta can fetch it. Size and format limits are Meta’s, and they differ per channel.

The 24-hour window

Meta only lets you message freely within 24 hours of the customer’s last message. After that:

WhatsApp — you must use an approved template. See Templates.
Instagram — you can send outside the window with the human agent tag, by passing "humanAgent": true. Use it only when a person is actually replying; misusing it puts the channel at risk.

Balance

Each outbound message draws from your prepaid wallet at Meta’s conversation rate. Without enough balance the call returns 402 and nothing is queued. Inbound messages are never blocked by balance.