GoliathDevelopersGet an API key
Reference/Contactsgenerated from the gateway manifest

dismissContactSuggestion

Dismiss a suggestion card with the reason the person gave.

POST/api/v1/callWRITEidempotent · 24 hruns as the key's owner
View as Markdown

Dismiss a suggestion card with the reason the person gave (NOT_RELEVANT, WRONG_TONE, WRONG_FACTS, ALREADY_DONE, OTHER, …). Recorded through the API, not as feedback heard from a person.

curl https://server.goliathdata.com/api/v1/call \
  -H "Authorization: Bearer $GOLIATH_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
    "operationId": "dismissContactSuggestion",
    "variables": {
      "suggestionId": "<suggestionId>",
      "reason": "NOT_RELEVANT"
    }
  }'
import { GoliathClient } from '@goliath-data/sdk'

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

// Enum values as strings: the SDK's enum types aren't exported yet, so assert to the method's variables type.
const variables = {
  suggestionId: '<suggestionId>',
  reason: 'NOT_RELEVANT'
} as Parameters<typeof goliath.contacts.dismissContactSuggestion>[0]

const result = await goliath.contacts.dismissContactSuggestion(variables, { idempotencyKey: crypto.randomUUID() })
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',
    'Idempotency-Key': crypto.randomUUID(),
  },
  body: JSON.stringify({
    operationId: 'dismissContactSuggestion',
    variables: {
      suggestionId: '<suggestionId>',
      reason: 'NOT_RELEVANT'
    }
  }),
})
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.

suggestionIdID!required
reasonContactSuggestionDismissReason!required
NOT_RELEVANTWRONG_TONEWRONG_FACTSALREADY_DONEOTHERNO_LONGER_DISTRESSEDWRONG_PROPERTYNOT_MY_LEADWRONG_PERSONESTATE_ALREADY_HANDLEDSTILL_OWNSKEPT_MINESHOULDNT_MESSAGE

Response

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

response shape
{
  "data": {
    "contactSuggestionMutation": {
      "dismissContactSuggestion": {
        "id": "<ID>",
        "status": "PENDING"
      }
    }
  }
}

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.

409idempotency_conflict

A request with this Idempotency-Key is still in flight.

Idempotency

Send an Idempotency-Key of 1 to 255 characters. A finished request retried with the same key replays its stored response, marked Idempotency-Replayed: true; one still in flight returns 409 idempotency_conflict. Keys expire after 24 hours. Write without fear →

READgetContactREADgetContactsPropertiesREADfindContactsByNoteREADsearchInteractionsREADcountContactsREADfindContacts