Last updated 3 minutes ago

Best practices

This article describes some best practices for working with Attentive’s webhooks.

Event types

Your webhook endpoints should be configured to receive only the types of events required by your integration. We don’t recommend configuring the webhook to listen for additional events (or all events) because it could put undue strain on your server.

Order of events

Attentive does not guarantee delivery of events in the order in which they are generated. For example, a subscribe event will trigger a SMS message send event.

Your endpoint should not expect delivery of these events in this order and should handle this accordingly.

Delivery attempts and retries

When your webhook is enabled, it delivers your webhook events for up to three days with an exponential back off. If the request surpasses those three days, we no longer attempt to deliver that request.

If your endpoint was disabled or deleted when we attempted a retry, future retries of that event are prevented.

Disable logic

Attentive attempts to notify you of a misconfigured endpoint through email if an endpoint has not responded with a 2xx HTTP status code for multiple days in a row.

If the endpoint continues to fail for multiple days in a row, we notify you to let you know that your webhook was automatically disabled.