Bring Hypeline into
the flow of work.

Add one URL as a source and start surfacing deduplicated new content from it

Remove a source and stop surfacing changes from it

Remove up to 200 sources in one request. Each ID reports its own outcome, so one bad ID never aborts the batch.

Retrieve one source by its ID

List the sources this key can see, with detected tier, health, and tags

Create a keyword or Boolean query matched against the content of changes

Delete an alert and stop matching; attached destinations are detached, not deleted

List alerts with their query, watched source IDs, language, enabled state, bound destinations, and recent match activity

Replace an alert definition: query, watched sources, language, and enabled state

Attach a destination that already exists to another alert, optionally with a cadence that applies to this alert only. The same channel can be instant for one alert and daily for another. The destination, its signing secret and its other alerts are untouched.

Attach a delivery target under an alert: webhook, Slack, Discord, Telegram, or ntfy. Using a channel you already have reuses that destination rather than duplicating it, and a reuse returns no secret, because the original was revealed once at creation.

Register a delivery target that is attached to no alert yet. It receives nothing until it is attached, so use it to set a channel up front and attach it to one or more alerts afterwards.

Delete the destination itself, with its signing secret and delivery history. It stops delivering for every alert it is attached to. To stop delivering to one alert only, use Detach.

Detach a destination from one alert. The destination itself, its signing secret and its other alerts are untouched, so a channel shared with another alert keeps delivering for that alert.

List delivery destinations with delivery health and every alert each one delivers for

Replace a delivery destination definition. A destination is one shared object, so every edit applies to every alert attached to it.