---
title: "Needs Support"
method: POST
path: "/notifications/engagements/needs-support"
tags: ["engagements"]
---

# Needs Support

`POST /notifications/engagements/needs-support`

## Request

- Base URL: `https://api-docs.upsmith.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api-docs.upsmith.com/notifications/engagements/needs-support`
- Auth: one of:
  - API key in header `x-api-key`
  - HTTP bearer

## Query parameters

- `engagement_id` string, required
- `summary` string, required
- `support_reason` string, nullable

## Headers

- `organization-id` string, nullable
- `x-user-id` string, nullable
- `timezone` string
- `x-actor-email` string, nullable
- `x-request-source` string, nullable
- `x-operation-id` string, nullable
- `x-commit-message` string, nullable
- `x-confirmation-id` string, nullable
- `x-chat-id` string, nullable

## Request body

- NeedsSupportRequest: Body of the needs-support notification call. Subclasses the filters rather than nesting them so the wire shape stays a flat object: an old caller's filters-only body still validates, and a new caller's extra field is ignored by an older reader. That is what lets agent-service and api-service roll out in either order.
  - `agent_v2_ids` string[]
  - `roster_ids` string[]
  - `transcript_summary` TranscriptSummaryTurn[], nullable
    - `role` string, required
    - `origin` string, required
    - `content` string, required
    - `created_at` string, date-time, nullable
  - `transcript_summary_truncated` boolean

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/upsmith/apis/upsmith-api.md) - [All operations](https://skmtc.dev/upsmith/apis/upsmith-api/llms.txt) - [OpenAPI document](https://skmtc.dev/upsmith/apis/upsmith-api/revisions/86e2c2bd93af?raw)