---
title: "Send SMS to Lead"
method: POST
path: "/communications/send_sms/lead"
tags: ["SMS"]
---

# Send SMS to Lead

`POST /communications/send_sms/lead`

Send a message to a Lead via SMS.

## Headers

- `x-api-key` string, required

## Request body

- RequestSMSLead — Contains the needed attributes to send an SMS to Lead
  - `send_from_group_phone_number_id` integer, required — group number id, use the GET group_phone_numbers endpoint to get the list
  - `send_to_lead_id` integer, required
  - `body` string, required — message body

## Response `200`

Message Identifier

- ResponseSMSLead — single message response
  - `send_from` SendFromSMS — send_sms send_from info
    - `send_from_group_phone_number_id` string — phone number id
    - `send_from_group_phone_number` string — phone number
    - `send_from_group_phone_number_name` string — name of customer
  - `send_to` RecipientSMSLead, required — additional name field to request recipient structure
    - `send_to_lead_id` string
    - `send_to_name` string — name
  - `body` string, required — message body
  - `conversation_id` string — twilio conversation sid
  - `message_id` string — twilio message sid
  - `message_status` string — twilio delivery_receipt message status: sent, delivered, failed, undelivered
  - `sent_datetime` string, date-time — Datetime message was sent
  - `error` string — if there was an error
  - `wodify_validation_result` string — The purpose of this attribute is to save any UserException message, that is, and user friendly message that should be shown to the end user. All methods should have, just like service actions: - an UserException with Abort Transaction = Yes, and a Log Error = No - an AllExceptions with Abort Transaction = Yes, and a Log Error = Yes With this, any known issue that we don&#39;t consider an error log, like a business validation, we raise it to be catch in the UserException and we don&#39;t log it. Then, in the OnResponse of the full REST service, the Build_Response_JSON action will take care on the output json format. An Exception will have the default formatted error message. If its an AllException, it will log the error so that we can fix it. If its a UserException, it will deliver as an error but it won&#39;t log it as an error. A success output will not have this attribute, the Build_Response_JSON will remove it from the final output.

---

[API](https://skmtc.net/wodify/apis/leads.md) · [All operations](https://skmtc.net/wodify/apis/leads/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/wodify/leads/revisions/974500ca0714/schema)
