Skip to main content
Webhooks allow external systems to receive real-time notifications about events in your Trackly SMS account.

​
Available Webhooks

​
Inbound: Delivery Status

Receive delivery status updates from SMS providers: 
POST https://app.tracklysms.com/api/webhook-feedbacks/infobip
This webhook receives:
  • Message delivery confirmations
  • Failure notifications
  • Carrier status updates
See Delivery Status Webhook for payload format.

​
Provider Webhooks

Trackly receives webhooks from your SMS providers:
ProviderWebhook Type
InfobipDelivery reports
TwilioMessage status callbacks
CMDelivery receipts
These are configured automatically when you set up your sending list.

​
Conversion Postbacks

Receive conversion data from affiliate platforms:

​
TUNE/HasOffers

Configure in TUNE: 
https://app.tracklysms.com/api/postbacks/tune?click_id={aff_sub}&payout={payout}

​
Everflow

Configure in Everflow: 
https://app.tracklysms.com/api/postbacks/everflow?click_id={sub1}&payout={revenue}

​
Custom Outbound Webhooks

Trackly supports outbound webhooks that send real-time event notifications to your systems. Outbound webhooks use the WebhookEndpoint configuration model with HMAC-SHA256 request signing for authenticity verification.

​
Supported Events

  • Message sent events
  • Click events
  • Conversion events
  • Opt-out events

​
Delivery & Retry

Outbound webhooks are delivered as HTTP POST requests with a JSON body and an X-Trackly-Signature HMAC-SHA256 header. If your endpoint returns a non-2xx status, Trackly retries up to 5 times with exponential backoff:
AttemptDelay
1st retry1 minute
2nd retry5 minutes
3rd retry15 minutes
4th retry1 hour
5th retry2 hours
Endpoints that fail consecutively are auto-paused to prevent unnecessary load.

​
Webhook Security

​
IP Whitelisting

Provider webhooks come from known IP ranges. Create a support ticket from your dashboard (Support > New Ticket) if you need IP lists for whitelisting.

​
Signature Verification

Some providers sign webhooks. Verify signatures to ensure authenticity.

​
HTTPS Required

All webhook endpoints use HTTPS for encrypted communication.

​
Error Handling

​
Retries

Most providers retry failed webhooks:
  • Initial attempt
  • Retry after 1 minute
  • Retry after 5 minutes
  • Retry after 30 minutes

​
Logging

Failed webhooks are logged. Create a support ticket from your dashboard (Support > New Ticket) if you’re missing data.

​
Testing Webhooks

​
Delivery Status

Send a test message and monitor for delivery confirmation.

​
Conversions

Use TUNE’s postback tester to verify conversion tracking.

​
Troubleshooting

Check:
  • Webhook URL is correctly configured
  • Endpoint is accessible and returns 200
  • No firewall blocking provider IPs
Ensure your handler is idempotent. Some providers may retry even on success.
Verify the postback URL includes all required parameters.

​
Next Steps

API Reference

Webhook payload format

TUNE Integration

Set up conversion tracking