---
title: "Actionable dating notices, ordered by urgency"
method: GET
path: "/api/v1/dating/notices"
---

# Actionable dating notices, ordered by urgency

`GET /api/v1/dating/notices`

## Request

- Base URL: `https://memchats.com`
- URL: `https://memchats.com/api/v1/dating/notices`
- Auth: HTTP bearer

Computed from the same rows and rules as the dating list. One notice per person, only when it is the user's turn: `she_asked` (she left a question unanswered), `cooling` (still for 2 days or more) or `your_turn`. Ordered by kind, then by days parked. `days` is null when the real time of the last message is unknown. Used by the Alerts screen of the FlirtMaster edition.

## Response `200`

The notices, most urgent first

- object
  - `notices` object[]
    - `contactId` integer
    - `name` string
    - `kind` 'she_asked' | 'cooling' | 'your_turn'
    - `days` integer, nullable

## Other responses

- `401`: Not signed in

---

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