---
title: "Dismiss Match"
method: POST
path: "/care-team/{care_team_member_id}/dismiss-match"
tags: ["care-team-match"]
---

# Dismiss Match

`POST /care-team/{care_team_member_id}/dismiss-match`

## Request

- Base URL: `https://api.projectindi.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.projectindi.com/care-team/{care_team_member_id}/dismiss-match`
- Auth: none declared

Parent dismisses an "already on indi" match suggestion ("not involved").

Stamps the durable ``suggestion_dismissed_at`` tombstone so the nudge is
never re-surfaced for this contact (checked before every enqueue + fan-out,
never cleared by reconcile). This is the PARENT-side counterpart to the
worker-side ``/decline-match``: ownership is enforced by RLS (the caller must
own the child the contact is on), so the user client suffices - a non-owner's
SELECT/UPDATE simply sees no row.

Idempotent: re-dismissing a dismissed row returns ``{success, idempotent}``.
404 when the contact is unknown or not the caller's.

Authentication: JWT required.

## Path parameters

- `care_team_member_id` string, required

## Response `200`

Successful Response

- object

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/projectindi/apis/indi-agent-api-first-principles.md) - [All operations](https://skmtc.dev/projectindi/apis/indi-agent-api-first-principles/llms.txt) - [OpenAPI document](https://skmtc.dev/projectindi/apis/indi-agent-api-first-principles/revisions/25a7813e21fd?raw)