---
title: "Get a saved reply"
method: GET
path: "/v1/projects/{project}/support/canned-replies/{reply}"
tags: ["Support Inbox"]
---

# Get a saved reply

`GET /v1/projects/{project}/support/canned-replies/{reply}`

## Request

- Base URL: `https://api.subscriby.net`
- URL: `https://api.subscriby.net/v1/projects/{project}/support/canned-replies/{reply}`
- Auth: HTTP bearer

One snippet. There is no `support-canned-reply:view`: a snippet is only ever read as part of the picker, so this route gates on `view-any` too. A reply is resolved **within the project**: another project's reply id is a `404 RESOURCE_NOT_FOUND`.

`shortcut` is `null` when the creator never set one; the snippet is then picked from the list rather than typed.

## Path parameters

- `project` string, uuid, required
- `reply` string, uuid, required

## Response `200`

The snippet.

- object
  - `data` SupportCannedReplyResource, required: A saved reply: a reusable snippet the support inbox composer expands from a shortcut or picks from a list.
    - `id` string, required: The snippet's id.
    - `project_id` string, required: The project the snippet belongs to.
    - `title` string, required: The label shown in the picker, 2 to 80 characters; never sent to the member.
    - `body` string, required: The text sent to the member when the snippet is used, 2 to 4,000 characters.
    - `shortcut` string, nullable, required: What the creator types in the composer to pull the snippet in, up to 30 letters, numbers, dashes and underscores, unique within the project; null when the snippet is picked from the list instead.
    - `sort_order` integer, required: The snippet's position in the picker, 0 to 999.
    - `created_at` string, nullable, required: When the snippet was created, ISO 8601.
    - `updated_at` string, nullable, required: When the snippet last changed, ISO 8601.

## Other responses

- `401`: `AUTHENTICATION_REQUIRED`: the request carries no bearer token, or one that is revoked, malformed, or minted for another environment (an `sbt_test_` token on production).
- `403`: `TOKEN_MISSING_ABILITY`: the token is valid but does not carry the ability this endpoint requires; `error.context.required_ability` names the one to grant. An endpoint that also checks who owns a row or which tier the account is on answers `FORBIDDEN`, `TEAM_TIER_REQUIRED` or `CONNECTOR_TIER_REQUIRED` with the same status, and says so in its own description.
- `404`: `RESOURCE_NOT_FOUND`: an id in the path names nothing the token can see. `TENANT_MISMATCH`: the project sits outside the token's `scope:project:` allow-list, or the token carries no team scope. Both answer 404 rather than 403 so that existence outside the token's scope cannot be inferred.
- `429`: `RATE_LIMITED`: the token has spent its 300 requests a minute or 10,000 an hour; `Retry-After` says when the next one is accepted.

---

[API](https://skmtc.dev/memberpass/apis/subscriby-rest-api.md) · [All operations](https://skmtc.dev/memberpass/apis/subscriby-rest-api/llms.txt) · [OpenAPI document](https://skmtc.dev/memberpass/apis/subscriby-rest-api/revisions/59c4df91d764?raw)