Webhooks

Webhooks notify you in real time of events related to your sends. As soon as an event occurs, Conexteo sends an HTTP request to the URL you have declared for the relevant type.

The three types

ack_sms: SMS delivery receipts (delivered, failed).

reply: inbound replies from recipients, SMS and RCS (including clicks on RCS suggestions).

ack_rcs: RCS statuses (delivered, read, failed, SMS fallback). Available in signed mode only.

Signed or unsigned mode

Unsigned: simple delivery, no delivery guarantee (see retries below).

Signed (recommended): every request carries an HMAC signature to verify, and benefits from retries. This is the required mode for ack_rcs.

Delivery and retries

Attempt success or failure
An HTTP 2xx response from your server = delivered. Any other status, a timeout or a network error = failed attempt.

Retries (signed webhooks only)
An unsigned webhook is sent once: if it fails, it is not retried. A signed webhook is retried up to 8 attempts in total, with an increasing delay between each:

After failure no.	Next attempt in
1	30 seconds
2	2 minutes
3	10 minutes
4	30 minutes
5	1 hour
6	4 hours
7	12 hours

That is a retry window of about 18 hours. After the 8th attempt without success, the delivery is abandoned (status failed).

Idempotency
The X-Conexteo-Webhook-Id header stays identical across all attempts of the same event. Process each identifier only once: this is your safeguard against duplicates.

Tracking
Check the status of your deliveries via GET /webhooks/deliveries (statuses: pending, delivered, failed, cancelled).

The three types#

Signed or unsigned mode#

Delivery and retries#

The three types

Signed or unsigned mode

Delivery and retries