API pipeline: See who viewed your card

Index: API pipelines — index

Goal: see how many people opened your card, which pages they viewed and where they came from.

Steps

1. Read the stats (you need write access to the card: its owner or an editor).

GET /v0/my/cards/{nonce | @handle}/stats?window_days=30
→ {"day":   {"views": 28,  "people": 11},
   "week":  {"views": 177, "people": 67},
   "month": {"views": 191, "people": 69},
   "timeline": [{"day": "2026-10-09", "views": 9, "people": 6}, …],
   "pages":    [{"key": "/@example-handle", "views": 32, "people": 18}, …],
   "from":     [{"key": "", "views": 77, "people": 49}, {"key": "/", "views": 24, "people": 14}, …],
   "sources":  [{"key": "telegram", "views": 5, "people": 4}, …],
   "mentions": [{"key": "article/470000000000000002", "views": 1, "people": 1}],
   "tile_shown": 36, "tile_opened": 4}

• day / week / month: the last 1, 7 and 30 days; timeline: one row per day for window_days (default 30).
• pages: viewed paths. For a project: its own page and every card that belongs to it; for any other card: its own page.
• from: where the view came from: a cabi.chat path, an external domain, or "" = direct.
• sources: utm_source values of the visits ("" = none).
• mentions (projects): cards opened from the project's mention links.
• tile_shown / tile_opened: how often the card's tile was shown in lists and opened from there.

Behind

• Humans only: bots and tools are left out; so are you and the card's owner.
• Visits are recorded since 2026-10-08.

Rules

• 401 without a token; 404 when the card is unknown or you may not edit it.

API surface