---
title: "Get Message/Campaign Recipients"
method: POST
path: "/get-sms-sent.json"
tags: ["Reporting"]
---

# Get Message/Campaign Recipients

`POST /get-sms-sent.json`

Get information about a message send and it's recipients
This will return paginated information regarding individual recipients on a campaign or message send.

## Response `200`

Successful response containing information about the sent message or campaign.

- object
  - `message` object — Information about a message or campaign that you have sent.
    - `message_id` integer — Numeric ID assigned to the message that was sent.
    - `send_at` string, date-time — Date and time that message was sent from your account. Returned in ISO8601 format YYYY-MM-DD HH:MM:SS in UTC Timezone.
    - `recipients` integer — Number of recipients message was sent to.
    - `cost` number — Total cost of all messages. Returned as value per account currency to 3 decimal places 0.000.
    - `sms` integer — Total number of message parts delivered. If the message is longer than 160 characters this will return count of all parts. Eg. if a 180 character message is delivered to 2 recipients. Value returned will be 4.
    - `message_content` string — Content of message sent.
    - `list` object — ID and name of list delivered to.
    - `delivery_stats` object — Report of messages delivered. Count of different reporting stats we collect. Delivery reports are marked using a DLR (Delivery Receipt) or Acknowledgement (ACK) returned from the carrier, a DLR is a handset level report and an ACK is simply a response from the carrier that the request was received. Global carriers have different functionality available. See our Global Delivery List for details.
      - `delivered` integer — Messages delivered.
      - `pending` integer — No delivery report received from carrier. Allow upto 72hrs or use validity in send-sms call to process.
      - `bounced` integer — Handset was disconnected, hard-bounce, or message was undeliverable due to handset switched off, out of range or other temporary deliverability issue, soft-bounce. For a specific bounced status use get-sms-sent.
      - `responses` integer — Replies received.
      - `optouts` integer — Recipients opted out, either by reply or unsub link.
  - `recipients` object — A paginated report of all the recipients delivered to in your message/campaign
    - `msisdn` integer — The mobile number of the recipient
    - `first_name` string — First name of recipient as stored in contacts
    - `last_name` string — Last name of the recipient as stored in contacts
    - `delivery_status` object
      - `delivered` integer — Message delivered to handset.
      - `pending` integer — No delivery report received from carrier. Allow upto 72hrs or use validity in send-sms call to process.
      - `bounced` integer — Handset was disconnected, hard-bounce, or message was undeliverable due to handset switched off, out of range or other temporary deliverability issue, soft-bounce. For a specific bounced status use get-sms-sent.
      - `responses` integer — Replies received.
    - `optout` integer — Set to true if recipient opted out.
  - `error` object — Error code and description.
    - `code` string — Error code.
    - `description` string — Description of the error.

---

[API](https://skmtc.net/kudosity/apis/transmit-sms-api.md) · [All operations](https://skmtc.net/kudosity/apis/transmit-sms-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/kudosity/transmit-sms-api/versions/9f6c34b849af/schema)