---
title: "List Signal Preferences"
method: GET
path: "/alerts/preferences"
tags: ["alerts"]
---

# List Signal Preferences

`GET /alerts/preferences`

## Request

- Base URL: `https://api.tickertrac.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.tickertrac.com/alerts/preferences`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-API-Key`

What the reader's own ratings are currently doing to their feed order.

Personalisation that changes what you see and cannot be inspected is the kind
people learn to distrust. This reports both dimensions -- kinds of signal and
companies -- with the rating count behind each and whether it is strong enough to
be acting at all, so "why is this near the bottom" has an answer that is not a
guess.

## Response `200`

Successful Response

- SignalPreferenceOut[]
  - `kind` 'source' | 'ticker', required
  - `value` string, required
  - `ratings` integer, required
  - `usefulness` number, required
  - `affects_ranking` boolean, required
  - `reset_at` string, date-time, nullable

---

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