Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.tracklysms.com/llms.txt

Use this file to discover all available pages before exploring further.

Trackly SMS receives delivery status updates from SMS providers via internal webhook endpoints. These are configured on the provider side to send delivery reports back to Trackly — they are not user-configurable webhooks.
These webhook endpoints are internal. They are configured by Trackly within each SMS provider’s dashboard so that delivery reports are routed back to the platform. You do not need to configure these yourself.

​
Webhook URLs

Each SMS provider has a dedicated webhook endpoint:
ProviderWebhook URL
Infobiphttps://api.tracklysms.com/api/webhook-feedbacks/infobip?account={account_id}
CMhttps://api.tracklysms.com/api/webhook-feedbacks/cm?account={account_id}
Twiliohttps://api.tracklysms.com/api/webhook-feedbacks/twilio?account={account_id}
Limehttps://api.tracklysms.com/api/webhook-feedbacks/lime/{webhook_secret}?account={account_id}
EZ Textinghttps://api.tracklysms.com/api/webhook-feedbacks/eztexting/{webhook_secret}?account={account_id}
Lime and EZ Texting do not support custom HTTP headers on outbound webhooks. To authenticate incoming callbacks, Trackly uses a per-provider path-segment secret ({webhook_secret}) compared constant-time against LIME_WEBHOOK_SECRET / EZTEXTING_WEBHOOK_SECRET on the server. Both values are managed in GCP Secret Manager. Configure your reverse proxy / access-log pipeline to redact the path segment under /api/webhook-feedbacks/{lime,eztexting}/ before forwarding logs downstream.

​
Query Parameters

​
account
string
required
The Trackly account ID associated with the delivery report. This parameter is included in the webhook URL so Trackly can route the delivery status to the correct account.

​
Webhook Payload

Infobip sends delivery status updates in the following format: 
{
  "results": [
    {
      "messageId": "msg_abc123def456",
      "to": "+14155551234",
      "status": {
        "groupId": 3,
        "groupName": "DELIVERED",
        "id": 5,
        "name": "DELIVERED_TO_HANDSET"
      },
      "doneAt": "2024-01-15T10:30:00.000+0000"
    }
  ]
}

​
Status Groups

Infobip uses status groups to categorize delivery outcomes:
Group IDGroup NameDescription
1PENDINGMessage is being processed
2UNDELIVERABLEMessage could not be delivered
3DELIVEREDMessage was delivered successfully
4EXPIREDMessage expired before delivery
5REJECTEDMessage was rejected by carrier

​
Common Status Codes

​
Delivered (Group 3)

IDNameDescription
5DELIVERED_TO_HANDSETDelivered to recipient’s phone
6DELIVERED_TO_OPERATORDelivered to carrier (no handset confirmation)

​
Undeliverable (Group 2)

IDNameDescription
7REJECTED_ABSENT_SUBSCRIBERRecipient not available
9REJECTED_SYSTEM_ERRORSystem error
14REJECTED_OPERATORRejected by carrier
15REJECTED_DUPLICATEDuplicate message

​
Rejected (Group 5)

IDNameDescription
51REJECTED_SPAMMessage flagged as spam
52REJECTED_DESTINATIONInvalid destination

​
Receiving Alerts

Instead of polling for status updates, you can receive real-time alerts in Discord:

Discord Alerts

Get notified of delivery failures in real-time

Configure Alerts

Customize which alerts you receive

​
Alert Types

When delivery failures occur, you can receive alerts via Discord:
Alert TypeTrigger
Delivery FailureMessage status is UNDELIVERABLE or REJECTED
Spam ComplaintMessage flagged as spam (status 51)
Opt-OutRecipient replied STOP
See Discord Alerts for configuration details.

​
Response

The Trackly webhook endpoint returns a 200 OK response to acknowledge receipt: 
{
  "status": "success"
}
If the webhook returns an error status, the SMS provider may retry the request. Trackly’s endpoints are designed to handle retries idempotently.