---
title: "Call contact.get"
method: POST
path: "/api/v1/tools/contact.get"
tags: ["contact"]
---

# Call contact.get

`POST /api/v1/tools/contact.get`

## Request

- Base URL: `https://app.goosybear.ai`
- URL: `https://app.goosybear.ai/api/v1/tools/contact.get`
- Auth: HTTP bearer

Say what we know about one customer — 'who is this lead?', 'what's the story with that contact?', 'have we talked to them before?'.  Read one customer's record — who they are, which ways exist to reach them, their tags, whether we may message them, and their recent history. Address them by their id, or by ONE key you already hold from the conversation (an email, a phone number, a Messenger id). It deliberately returns no addresses or phone numbers, and there is no way to list customers with it. The summary is small on purpose; ask for section timeline or notes when it says more exists. Not for writing on their record — that is `contact.note`.

Every result names the workspace it ran in. Say which workspace the answer is about. When the account has more than one workspace and none is selected, this tool refuses with `workspace_ambiguous` and lists the choices — offer them, never pick one.

## Headers

- `x-request-id` string

## Request body

- object
  - `contact_id` string, uuid: The customer to read, when you already have their id. Give EXACTLY ONE address: this customer id, or the identity pair (identity_kind WITH identity_value). Neither, or both together, is refused rather than guessed at.
  - `identity_kind` 'email' | 'phone' | 'meta_psid' | 'ig_id' | 'ghl_contact_id' | 'gbp_reviewer': Which kind of key this is: an email address, a phone number, a Messenger id (meta_psid), an Instagram id (ig_id), a CRM record id (ghl_contact_id), or a Google reviewer id.
  - `identity_value` string: The key exactly as you observed it. It is normalised before it is looked up, so capitals in an address are fine — but a phone number without its country code cannot be matched and will be refused rather than guessed at.
  - `identity_scope` string: The Meta PAGE id the key was seen on. REQUIRED for meta_psid and ig_id — those ids are only unique within one page, so without it nothing can be matched. Leave it out for every other kind.
  - `section` 'summary' | 'timeline' | 'notes': Which part to read. summary (the default) is the record plus the newest few history rows and notes; timeline is the recent history only; notes is their notes only. Ask for timeline or notes when the summary says more exists.
  - `workspace` string: Which workspace to run in — its slug. Omit to use your default. With more than one reachable workspace and no default, the call is refused and the choices are listed.

## Response `200`

The call was admitted and dispatched. `ok` says whether the tool succeeded — a refusal the tool itself produced is still a 200, exactly as it is a successful JSON-RPC result over MCP.

- union
  - object: The tool ran and answered.
    - `ok` true, required
    - `found` boolean, required
    - `section` 'summary' | 'timeline' | 'notes', required
    - `reason` string, required
    - `contact_id` string, nullable, required
    - `display_name` string, nullable, required
    - `stage` string, nullable, required
    - `origin` string, nullable, required
    - `first_seen_at` string, nullable, required
    - `last_seen_at` string, nullable, required
    - `reach` object[], required
      - `kind` string, required
      - `label` string, required
      - `verified` boolean, required
    - `reach_summary` string, nullable, required
    - `tags` string[], required
    - `consent` object, required
      - `label` string, required
      - `tone` 'ok' | 'blocked' | 'unknown', required
    - `crm` object, required
      - `section` 'on' | 'off', required
      - `connected` boolean, required
      - `last_synced_at` string, nullable, required
    - `timeline` object[], required
      - `id` string, required
      - `lead` string, required
      - `detail` string, required
      - `stamp` string, required
      - `by` string, required
      - `occurred_at` string, required
    - `timeline_truncated` boolean, required
    - `notes` object[], required
      - `id` string, required
      - `body` string, required
      - `source` string, required
      - `created_at` string, required
    - `notes_truncated` boolean, required
    - `degraded` string[], required
    - `workspace` string, required: The slug of the workspace this call ran in.
    - `working_in` object, required: Which workspace this call ran in, and how that was decided. Present on every workspace-scoped result.
      - `label` string, required: The chip words — e.g. "working in: Acme Main".
      - `note` string, required: Why this workspace — e.g. "your default", "this call only".
      - `workspace` string, required: The resolved workspace's slug.
      - `source` 'call-override' | 'key-pin' | 'stored-default' | 'sole-reachable', required: Which rung of the R7 precedence resolved the workspace.
  - ToolRefusal: A call that was admitted and dispatched, and did not succeed.
    - `ok` false, required
    - `code` string, required: The typed reason — e.g. `workspace_ambiguous`, `invalid_arguments`, or the tool's own failure code.
    - `message` string, required: A sentence a person can act on.
    - `workspaces` string[]: On a workspace refusal: the slugs this key may pass as `workspace`.
    - `issues` object[]: On `invalid_arguments`: which fields failed, and why.
      - `path` string, required
      - `message` string, required
    - `path` string: On an authoring refusal: where in your call's input it points, e.g. `steps.<key>.params.<field>`.
    - `fix` string: On an authoring refusal: the change to your call that would pass.
    - `instruction` string: On an authoring refusal: what to do next with it.

## Other responses

- `400`: The request could not be used: the body is present but not a JSON object (`tenant_api.malformed_body`); it is a top-level array carrying more messages than this endpoint accepts (`tenant_mcp.batch_too_large`); or the `Idempotency-Key` header is malformed (`tenant_api.idempotency_key_invalid`), disagrees with the body's `idempotency_key` (`tenant_api.idempotency_key_conflict`), or was sent to an action that cannot replay a retry (`tenant_api.idempotency_unsupported`). Nothing ran.
- `401`: No bearer credential, or one that did not resolve. Deliberately ONE undifferentiated answer for absent / unknown / revoked / expired, so the endpoint is never an oracle over the key space.
- `403`: The credential is good but the surface is not open to it — the platform or account API switch is off, or the holder lacks the `api.access` capability. The `code` says which.
- `404`: No such tool. The body names no tool and is identical for every unrecognised name.
- `429`: Over this key's per-minute cap. Carries `Retry-After` and `error.retry_after_seconds`.

---

[API](https://skmtc.dev/goosybear/apis/goosy-bear-api.md) · [All operations](https://skmtc.dev/goosybear/apis/goosy-bear-api/llms.txt) · [OpenAPI document](https://skmtc.dev/goosybear/apis/goosy-bear-api/revisions/0e033701d3f7?raw)