---
title: "Mark Match Clicked"
method: POST
path: "/api/v1/alerts/matches/{match_id}/clicked"
tags: ["alerts"]
---

# Mark Match Clicked

`POST /api/v1/alerts/matches/{match_id}/clicked`

## Request

- Base URL: `https://api.alert.camp` (the document declares no server; this is the origin it was published from)
- URL: `https://api.alert.camp/api/v1/alerts/matches/{match_id}/clicked`
- Auth: none declared

Record that the user tapped "Book" on a match (booking click-through).

Stamps ``clicked_at`` the first time only (idempotent — later taps don't
overwrite). This is the last event we own before the user leaves for the
provider's reservation site, so comparing ``clicked_at`` against
``booked_at`` reveals "tapped Book but the spot was already gone".

The mobile client fires this fire-and-forget right before opening the
booking URL, so it must stay cheap and must never block that redirect —
an unknown/foreign match_id is treated as a no-op (``updated: 0``) rather
than an error.

## Path parameters

- `match_id` string, required

## Headers

- `authorization` string, nullable
- `x-dev-user-id` string, nullable
- `x-app-version` string, nullable

## Response `200`

Successful Response

- object

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/alert/apis/alertcamp.md) · [All operations](https://skmtc.dev/alert/apis/alertcamp/llms.txt) · [OpenAPI document](https://skmtc.dev/alert/apis/alertcamp/revisions/864c8c9ef833?raw)