Regenerate Signals

Alias for context generate — signals are embedded in the situation-room payload.

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

Generate War Room Signals

cURL

curl --request POST \
  --url https://api.example.com/deals/{deal_id}/war-room/signals/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.

Literally calls the same handler as Regenerate Situation-Room Context — there’s no separate signals table; signals are embedded fields inside the same context payload. Identical request/response.

Auth

Same as the handler it aliases: a CRM manage scope (any *:manage, e.g. deals:manage) and an active organization on the token, on top of the deals_war_room flag.

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