Get message summary for a contact
Returns aggregate message counts, time bounds, channels used, and per-channel success/fail scores (each as a percentage 0-100 of messages on that channel) for one of your contacts. Successful terminal states: SENT/DELIVERED/READ for outbound, RECEIVED for inbound. Fail: FAILED.
contactId*stringuuidx-profile-id?stringProfile UUID to scope the request to a child profile. Only organization API keys can use this header. The profile must belong to the calling organization.
uuidSummary returned successfully
application/json- response
Standard API response envelope for all v3 endpoints
success?booleanIndicates whether the request was successful
data?|nullThe response data (null if error)
error?|nullError details (null if successful)
meta?Metadata about the request and response
curl -X GET 'https://api.sent.dm/v3/contacts/6ba7b810-9dad-11d1-80b4-00c04fd430c8/message-summary'{ "success": true, "data": { "contact_id": "6ba7b810-9dad-11d1-80b4-00c04fd430c8", "message_count": 42, "first_message_at": "2026-10-13T15:32:26.7836872+00:00", "last_message_at": "2026-11-12T12:32:26.7836996+00:00", "channels_used": [ "sms", "whatsapp" ], "channel_scores": [ { "channel": "sms", "success_score": 91, "fail_score": 9 }, { "channel": "whatsapp", "success_score": 90, "fail_score": 10 } ] }, "error": null, "meta": { "request_id": "req_7X9zKp2jDw", "timestamp": "2026-11-12T15:32:26.7837588+00:00", "version": "v3" }}Delete a contact DELETE
**Deprecated.** Use `PATCH /v3/contacts/{id}` with `{"opt_out": true}` instead, and expect this to be removed in a future release. It still behaves exactly as before, so nothing needs to change today. Opting a contact out stops every send to them, which is what deleting one was mostly used for — and it keeps the record of who they were and that they asked. A delete discards the consent history along with the contact, which is the part you need if anyone ever asks why you stopped, or why you started again. Dissociates a contact from the authenticated customer.
Template Definition
Reference for the Sent template definition JSON: header, body, footer, button, and variable fields, content rules and limits, and template statuses.