GoliathDevelopersGet an API key
Reference/Spacesgenerated from the gateway manifest

listSpaceContactFiles

Records › Contact files.

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

Records › Contact files: attachments and voicemails contacts sent or received, newest first. Filter by contactId, dealId (any contact on the deal), channel, direction, or query (the file's or the contact's name). Only files whose contact you may open. Each row's source says where it came from (a text thread, an email subject, a call). Page with after = nextCursor.

curl https://server.goliathdata.com/api/v1/call \
  -H "Authorization: Bearer $GOLIATH_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "operationId": "listSpaceContactFiles",
    "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.spaces.listSpaceContactFiles({})
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: 'listSpaceContactFiles',
    variables: {}
  }),
})
const { data, errors } = await res.json()

limit is clamped to 50.

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.

filterSpacesContactFilesFilter
channelSpacesContactFileChannel

Where a contact file came in.

TEXTEMAILVOICEMAIL
contactIdID
createdAfterDateTime

Only files that came in after this moment.

pipelineItemIdID

Files from any contact on this deal.

dealIdID
directionSpacesRecordDirection

Which way a record moved, from the organization's side.

RECEIVEDSENT
queryString

Matches the file name, the contact's name, or the words a texted file came with.

limitInt

Default 50.

afterString

Response

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

response shape
{
  "data": {
    "spacesQuery": {
      "records": {
        "contactFiles": {
          "nodes": [
            {
              "id": "<ID>",
              "name": "…",
              "contentType": "…",
              "createdAt": "2026-01-01T00:00:00.000Z",
              "contact": {
                "id": "<ID>",
                "name": "…"
              },
              "source": {
                "channel": "TEXT",
                "direction": "RECEIVED",
                "textConversationId": "<ID>",
                "phoneNumber": "…",
                "emailSubject": "…",
                "callId": "<ID>"
              }
            }
          ],
          "hasNextPage": true,
          "nextCursor": "…"
        }
      }
    }
  }
}

Errors

400unknown_variable

A variable the operation does not declare. A typo is refused rather than silently dropped.

401unauthorized

No bearer header, or the key is invalid or revoked.

403insufficient_scope

The key lacks the scope the operation requires.

403forbidden

A referenced record does not exist, was deleted, or is outside your organization. The gateway cannot tell those apart.

Behaviour

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

READlistSpaceRootsREADlistSpaceFolderREADgetSpaceItemREADsearchSpaceItemsREADgetSpaceTextContentREADgetSpaceTextLines