API: Sending messages

Business-initiated WhatsApp messages must use an approved template — that rule applies to the API exactly as it does in the app. The API lets your systems send those templates: order confirmations, booking reminders, shipping updates.

See the API overview for authentication and errors.

List approved templates — GET /v1/templates

curl -s https://app.nybero.com/api/v1/templates \
  -H "Authorization: Bearer $NYBERO_KEY"

[
  {
    "id": "7b1f…",
    "name": "order_confirmation",
    "language": "de",
    "category": "utility",
    "status": "approved",
    "variables": ["contact.name", "order_number"],
    "has_media_header": false
  }
]

Only approved templates are returned — those are the only ones that can be sent. variables lists the template’s placeholders in order; has_media_header tells you the template carries an image/video/document header (the saved header media is attached automatically at send time).

Send a template — POST /v1/messages/template

Identify the template by template_id or by template_name (optionally with language), and the recipient by contact_id or phone (the contact must already exist — create it first via POST /v1/contacts):

curl -s https://app.nybero.com/api/v1/messages/template \
  -H "Authorization: Bearer $NYBERO_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "phone": "+4915112345678",
    "template_name": "order_confirmation",
    "language": "de",
    "params": ["", "A-1042"]
  }'

{
  "message_id": "3f7a…",
  "contact_id": "0d9f…",
  "template": "order_confirmation",
  "status": "sent"
}

params supplies the values for the template’s variables, in order. Contact-field variables (contact.name, contact.phone) fill themselves per recipient — pass an empty string in that position (or any value; it is ignored). Custom variables use exactly what you send.

The send appears in the contact’s conversation in the Inbox like any other outbound message, and delivery/read receipts update its status there.

What the API enforces

The same guardrails as the app — expect these errors:

Status	Reason
409	The contact opted out — the API never messages opted-out contacts
409	The number is known not to be on WhatsApp
400	Template not approved, or its channel is not usable
402	Subscription inactive or the workspace’s monthly send limit is reached
502	Meta rejected the send — detail carries Meta’s error message

Note

Costs: template sends are billed by Meta directly to your Meta Business account, exactly like sends from the app — category and destination country set the price. See WhatsApp costs.

Tip

Sending to many people? The API send is built for transactional, one-recipient-at-a-time messages triggered by your systems. For a bulk send to an audience, use a campaign — it rate-limits, skips opt-outs in bulk and gives you delivery stats. For multi-step sequences, enrol the contact into an automation instead and keep the messaging logic visible in Nybero.

Worked example: booking reminder from your calendar system

Your booking tool knows the appointment; Nybero sends the reminder:

1. Create/refresh the contact at booking time: POST /v1/contacts with opt_in: true (consent collected in the booking form).
2. 24 hours before the slot, your scheduler calls POST /v1/messages/template with template_name: "appointment_reminder" and params carrying date and time.
3. Replies land in the shared Inbox, inside the 24-hour window — your team (or the AI agent) takes it from there.