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

Custom outbound webhooks (Trackly sending events to your system) are coming soon.
Future support for:
  • Message sent events
  • Click events
  • Conversion events
  • Opt-out events

Webhook Security

IP Whitelisting

Provider webhooks come from known IP ranges. Contact support for IP lists if you need to whitelist.

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. Contact support 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