# List the merge fields a blast can use

The names a blast aimed at one board may be written with: `?definitionKey=leads` answers `fields` as `[{name, label, group}]` — the recipient's names, the board's identity fields (`lead.name`, `lead.email`…) and every column under its slugged label ("Requested Amount" is `requested_amount`) — and `syntax`, the grammar: `{{first_name}}` for a field, `{{first_name|lead.name|"there"}}` for an either/or that tries each step and ends on the quoted words. Identity numbers and credit facts are never offered. It also answers `addressColumns`: the board's phone and email columns — and the plain text or number columns whose label says they hold one, as an imported board's do — as `[{id, label, kind, default}]`, which is what `addressColumnId` on `post_blasts_id_audience_board` may name. Read it before writing a blast's words so every field named is one the audience can fill.

Access class: `workspace`.

## Endpoint

`GET /v1/blasts/merge-fields`

## Parameters

| Name | In | Type | Required |
| --- | --- | --- | --- |
| definitionKey | query | string | Yes |

## Responses

### 200

the action's answer

Content type: `application/json`.

```json
{
  "data": {
    "addressColumns": [
      {
        "default": true,
        "id": "",
        "kind": "string",
        "label": "string"
      }
    ],
    "fields": [
      {
        "group": "string",
        "label": "string",
        "name": "string"
      }
    ],
    "syntax": {
      "eitherOr": "string",
      "field": "string",
      "rule": "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"
}
```
