Communications Webhook
The Communications webhook provides updates whenever an interaction occurs between CollectWise and a debtor. This includes inbound and outbound SMS or email messages, as well as notifications when a phone call has taken place. Note that phone call events do not specify whether the call was inbound or outbound. The webhook also includes the total number of SMS, emails, or phone communications sent to date.Webhook Notification
The webhook sends a payload containing the details of the communication, including the debtor ID, type of communication, and timestamp. Note: Phone call events do not include a direction attribute.Example Payloads
SMS Example:Inbound SMS Replies
When a consumer replies to a text you sent through the Texting endpoints, thecommunication object also carries the message itself and identifies which of your sends it answers. Here debtorId is the reference you supplied when sending.
Inbound Reply Example:
message is the reply text and from is the consumer’s number. messageId identifies this reply, and inReplyTo is the messageId that Send a Text returned for the message being answered. mediaUrls is only populated for MMS.
Note: inReplyTo is null when the reply cannot be matched to one of your sends, such as a consumer texting in cold or a conversation idle more than 7 days. debtorId is “UNKNOWN” if the number has no send on record. Inbound reply events do not include totalCommunications.
Delivery
Respond2xx. A failed delivery is retried up to 3 times, so the same event may arrive more than once. Use communication.messageId to de-duplicate. To recover inbound replies missed while your endpoint was down, use List Text Messages with the since parameter.
Each request is signed with an X-CollectWise-Signature header so you can confirm it came from us. We provide the signing secret and verification details when we set up your endpoint.
Send us your endpoint to configure this webhook for your integration.