---
title: "Reply"
method: POST
path: "/v1/teams/{team_id}/push/reply"
tags: ["push"]
---

# Reply

`POST /v1/teams/{team_id}/push/reply`

The owner typed back on a banner. With an `askId` the words ARE the
answer to that press; without one they are a message from the owner, and
the desk wakes on the team's `push_reply` hook — the same road the phone
connecting takes, so the exchange stays one conversation.

## Path parameters

- `team_id` string, uuid, required

## Headers

- `authorization` string, nullable
- `x-darwin-token` string, nullable

## Request body

- ReplyRequest — What the owner typed into a banner: an answer to a waiting ask, or — with no `askId` — a message to the desk about the notification named.
  - `askId` string, nullable
  - `text` string, required
  - `title` string, nullable
  - `channel` string, nullable
  - `place` string, nullable

## Response `200`

Successful Response

- object

## Other responses

- `422` — Validation Error

## Changes

> 32 revisions in range; 1 not diffed.

- **2026-09-11** `79b0c0f35170` — 1 info
  - endpoint added

[Change history](https://skmtc.dev/stormy/apis/stormy-control-plane/changes/v1/teams/:team_id/push/reply/post.md)

---

[API](https://skmtc.dev/stormy/apis/stormy-control-plane.md) · [All operations](https://skmtc.dev/stormy/apis/stormy-control-plane/llms.txt) · [OpenAPI document](https://skmtc.dev/stormy/apis/stormy-control-plane/revisions/b09e3c4ee2af?raw)