---
title: "Honeypot Recent"
method: GET
path: "/v1/stream/honeypot/recent"
tags: ["stream"]
---

# Honeypot Recent

`GET /v1/stream/honeypot/recent`

## Request

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

Poll fallback for clients that can't hold an open SSE connection — recent
honeypot births + rug-watch downgrades as JSON.

Requires auth (same gate as the SSE endpoint — not in ``PUBLIC_PREFIXES``).
``?since=<cursor>`` pages forward from a prior response's ``next`` cursor; a bare
call returns the most recent ``limit`` across both streams, PLUS a fold of recent
adverse ``honeypot_checks`` rows so the tape stays fresh when the narrow
HONEYPOT-band redis producer is quiet. Returns ``{"events": [...], "next":
"<cursor>", "count": N}`` where each event carries its ``type``, the source
fields, and its ``id`` (redis id, or ``hc:<row>`` for a folded check).

## Query parameters

- `since` string, nullable
- `limit` integer

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

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