Regenerate Situation-Room Context

POST /deals/{deal_id}/war-room/context/generate

Generate War Room Context

cURL

curl --request POST \
  --url https://api.example.com/deals/{deal_id}/war-room/context/generate \
  --header 'Authorization: Bearer <token>'

422

{
  "detail": [
    {
      "loc": [
        "<string>"
      ],
      "msg": "<string>",
      "type": "<string>"
    }
  ]
}

Gated by the live, per-user feature flag deals_war_room — 403 when disabled for the caller.

Synchronous — blocks until the analysis (and LLM enrichment pass) finishes and returns the final payload directly, unlike the placeholder-and-poll pattern used by Generate a Competitive Brief and Generate a Deal Brief.

Builds a deterministic signal-analysis base from the deal’s recent activities and stakeholder snapshot (genuine/cheap-talk/risk signal buckets with a 14-day time-decay weighting, coalition strength, win-probability adjustment, stakeholder map), then layers an LLM enrichment pass (Anthropic) on top that reclassifies the signal buckets — falling back to a still-non-empty heuristic enrichment when no Anthropic key is configured or the LLM output is invalid/too sparse (fewer than 2 signals). Upserts (delete-then-insert) the deal’s single deal_war_room_context row.

Auth

Requires a CRM manage scope and an active organization on the token. Any *:manage scope qualifies — in practice contacts:manage, deals:manage, companies:manage, or activities:manage.

Response

201 {success, payload, generated_at, source} — source is war_room_context_v2_signal_llm or war_room_context_v2_heuristic_signals depending on which path ran. See Get Situation-Room Context for the payload shape.

Authorizations

Authorization · string · header · required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

deal_id · string · required

The deal's id.

Response

201

application/json

Successful Response