---
title: "Publish an SMS"
method: POST
path: "/v1/design_studio/sms/{id}/publish"
tags: ["SMS link and publish"]
---

# Publish an SMS

`POST /v1/design_studio/sms/{id}/publish`

## Request

- Base URL: `https://api.customer.io`
- URL: `https://api.customer.io/v1/design_studio/sms/{id}/publish`
- Auth: none declared

If you made changes to a [linked SMS message](/integrations/api/design-studio/tag/sms-link-and-publish/linkSms/), you need to publish the SMS when you're ready so your workflows send the latest content.

## Path parameters

- `id` string, uuid, required

## Response `200`

SMS published

- ChannelPublishResponse: The result of the publish process.
  - `template_ids` integer[]: The IDs of the workflow templates that received the content.
  - `version_id` string: The identifier of the template version created by the publish process.

## Other responses

- `400`: The request is invalid due to malformed parameters, missing required fields, or constraint violations.
- `401`: Authentication failed due to a missing or invalid API key.
- `404`: The requested resource was not found.
- `422`: The liquid in the SMS's content or recipient isn't valid, so Customer.io doesn't publish it. Each error's `source.pointer` names the field that failed, as `/data/attributes/content` or `/data/attributes/recipient`. Fix the SMS, then publish it again.

## Changes

- **2026-10-08** `6378ded43e43`: 2 info
  - api tag `SMS link and publish` added
  - api tag `Design Studio SMS` removed
- **2026-10-06** `b0a0db5fbc21`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/customer/apis/customer-io-journeys-api-reference/changes/v1/design_studio/sms/:id/publish/post.md)

---

[API](https://skmtc.dev/customer/apis/customer-io-journeys-api-reference.md) - [All operations](https://skmtc.dev/customer/apis/customer-io-journeys-api-reference/llms.txt) - [OpenAPI document](https://skmtc.dev/customer/apis/customer-io-journeys-api-reference/revisions/ac0b282053fe?raw)