# record_signal

Record an observed buying signal with a one-line why-now and evidence URL. Duplicates return the existing signal, created:false. Suppressed people are refused.

| | |
| --- | --- |
| Group | Buying signals |
| Scope | `crm:write` |
| Who can call it | Agents and people with this scope. |
| Kind | Write. Recorded in the change history with who made it. |
| Retries | Pass `idempotency_key` (MCP) or the `Idempotency-Key` header (REST); a retry with the same key within 24 hours returns the first result. |
| Widget | In hosts that support MCP Apps, the result shows where the write landed (the changed record, the pipeline, or the updated list). |

## Parameters

| Parameter | Type | Required | Notes |
| --- | --- | --- | --- |
| `entity_type` | `company` \\| `person` | yes |  |
| `entity_id` | id (uuid) | yes |  |
| `type` | `complaint` \\| `post_engagement` \\| `hiring` \\| `job_change` \\| `funding` \\| `tech_adoption` \\| `headcount` \\| `news` \\| `ad` \\| `review` \\| `website_change` \\| `other` | yes |  |
| `summary` | string | yes | max 280 characters |
| `source` | string | yes | max 100 characters |
| `source_url` | string | yes |  |
| `observed_at` | date-time (ISO 8601 with offset) | no |  |

## Call it over MCP

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "record_signal",
    "arguments": {
      "entity_type": "company",
      "entity_id": "00000000-0000-4000-8000-000000000000",
      "type": "complaint",
      "summary": "…",
      "source": "…",
      "source_url": "…",
      "idempotency_key": "log-call-acme-2026-11-02"
    }
  }
}
```

Send it to `https://api.tandemcrm.app/mcp` (streamable HTTP). Most people never write this by hand: their agent picks the tool from its description.

## Call it over REST

```bash
curl -X POST https://api.tandemcrm.app/v1/ops/record_signal \
  -H "Authorization: Bearer $TANDEM_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: log-call-acme-2026-11-02" \
  -d '{"entity_type":"company","entity_id":"00000000-0000-4000-8000-000000000000","type":"complaint","summary":"…","source":"…","source_url":"…"}'
```

## Input schema

The JSON Schema the MCP server advertises for this tool (over MCP it also accepts `idempotency_key`):

```json
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "entity_type": {
      "type": "string",
      "enum": [
        "company",
        "person"
      ]
    },
    "entity_id": {
      "type": "string",
      "format": "uuid",
      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    },
    "type": {
      "type": "string",
      "enum": [
        "complaint",
        "post_engagement",
        "hiring",
        "job_change",
        "funding",
        "tech_adoption",
        "headcount",
        "news",
        "ad",
        "review",
        "website_change",
        "other"
      ]
    },
    "summary": {
      "type": "string",
      "minLength": 1,
      "maxLength": 280
    },
    "source": {
      "type": "string",
      "minLength": 1,
      "maxLength": 100
    },
    "source_url": {
      "type": "string",
      "pattern": "^https?:\\/\\/"
    },
    "observed_at": {
      "type": "string",
      "format": "date-time",
      "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"
    }
  },
  "required": [
    "entity_type",
    "entity_id",
    "type",
    "summary",
    "source",
    "source_url"
  ]
}
```