GoliathDevelopersGet an API key
Reference/Accountgenerated from the gateway manifest

listDirectMailLetters

The letters on contacts you can see.

POST/api/v1/callREADreadruns as the key's owner
View as Markdown

The letters on contacts you can see (Automations → Letters), newest first: totalCount, then a page (limit default 50, offset) of contactName, campaignLabel, workflowName, mode, status (QUEUED, SUBMITTED, MAILED, IN_TRANSIT, DELIVERED, RETURNED, CANCELED, FAILED…), requestedAt, mailedAt, deliveredAt. Narrow with statuses, modes (LIVE; a TEST account mails and bills nothing) or search (a contact or workflow name). The read for "did my letters go out", "how did the last mailer do" and "did anyone answer the mail": totalCount 0 with no narrowing means no letter on a contact you can see was ever mailed (an account setup's test letter is not listed), so say that plainly and never guess. Answers show as the contact's own text, call or email afterwards, and QR scans as the physicalMail contact filter.

curl https://server.goliathdata.com/api/v1/call \
  -H "Authorization: Bearer $GOLIATH_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "operationId": "listDirectMailLetters",
    "variables": {}
  }'
import { GoliathClient } from '@goliath-data/sdk'

const goliath = new GoliathClient({
  apiKey: process.env.GOLIATH_API_KEY!,
  baseUrl: 'https://server.goliathdata.com',
})

const result = await goliath.account.listDirectMailLetters({})
const res = await fetch('https://server.goliathdata.com/api/v1/call', {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${process.env.GOLIATH_API_KEY}`,
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    operationId: 'listDirectMailLetters',
    variables: {}
  }),
})
const { data, errors } = await res.json()

Variables

The example sends only what the schema requires. Some operations also need one of several optional variables (one filter or another, say); the description above says which.

limitInt
offsetInt
statuses[DirectMailPieceDisplayState!]
QUEUEDSUBMITTINGSUBMISSION_UNKNOWNNOT_SUBMITTEDSUBMITTEDSCHEDULEDPRODUCINGMAILEDIN_TRANSITRE_ROUTEDNEAR_DELIVERYDELIVEREDRETURNEDCANCELEDFAILED
modes[DirectMailConnectionMode!]
TESTLIVE
searchString

Response

What comes back under data: a list shows as one entry, and a value as its type.

response shape
{
  "data": {
    "contactQuery": {
      "directMailLetters": {
        "totalCount": 0,
        "nodes": [
          {
            "id": "<ID>",
            "contactId": "<ID>",
            "contactName": "…",
            "provider": "OPEN_LETTER_CONNECT",
            "campaignLabel": "…",
            "mode": "TEST",
            "status": "QUEUED",
            "refusalReason": "…",
            "requestedAt": "2026-01-01T00:00:00.000Z",
            "mailedAt": "2026-01-01T00:00:00.000Z",
            "deliveredAt": "2026-01-01T00:00:00.000Z",
            "workflowName": "…"
          }
        ]
      }
    }
  }
}

Errors

Behaviour

A read. It rejects an Idempotency-Key header with 400 bad_request.