# List the placeholders a message template can use

The placeholder vocabulary a message or document template may draw on — the tokens that resolve against a record when a template is rendered, and what each one stands for. Read it before writing a template, so a token that resolves to nothing is never sent to a merchant. Read-only for everyone: growing this list is a schema change, not a write.

Access class: `workspace`.

## Endpoint

`GET /v1/message-placeholders`

## Parameters

| Name | In | Type | Required |
| --- | --- | --- | --- |
| body | query | null | No |
| params | query | object | No |
| query | query | object | No |

## Responses

### 200

the action's answer

Content type: `application/json`.

```json
{
  "data": [
    {
      "description": "string",
      "group": "string",
      "label": "string",
      "name": "string"
    }
  ]
}
```

### default

a refusal: `{"error": "<what a person needs to read>"}`. 401 no credential, 402 the plan does not include this, 403 the seat does not, 404 the thing does not exist or is not yours to see.

Content type: `application/json`.

```json
{
  "error": "string"
}
```