As a Power User, you have access to several advanced features to enhance your monitoring capabilities.
The following flags are exclusively available to Power Users:
| in-title | Only search in the submission's title. |
| in-url | Only search in the submission's URL. |
| in-body | Only search in the submission's body text. |
| in-username | Only search in the author's username (username is not searched without this flag). |
| in-permalink | Only search in the post or comment's permalink (permalink is not searched without this flag). |
| full-text | Return the full text of a post or comment instead of an excerpt. |
| instant | Bypass the account's email delay and send the alert immediately. |
| exclude=word | Exclude matches where the surrounding text contains "word". |
| include-any=word | Match if text also contains at least one 'include-any' word. |
| include-all=word | Match if text also contains all 'include-all' words. |
| exclude-username=word | Exclude matches posted by a given user (exact match only). |
The `in-` flags can be combined to search in multiple fields (e.g., in-title in-url). If no `in-` flags are specified, the title, body, and URL are searched by default.
group=
The group=name flag allows you to organize your alerts into separate, dedicated emails. All alerts with the same group name will be bundled into a single email, separate from your other alerts. This is useful for managing alerts for different projects or topics.
For example:
"Tesla" group=stocks"Nvidia" group=stocks"Apple" group="tech companies"If a group name contains spaces, it must be enclosed in double quotes.
Group names also allow you to filter alerts on the dashboard and in RSS and JSON feeds.
Power Users can choose how and when alert emails are delivered. From your account page, you can select one of three modes:
When using scheduled dispatch, you can set your timezone to ensure emails arrive at the right local time.
Note: Alerts with the instant flag will always be sent immediately, regardless of your email settings.
The exclude=text flag allows you to prevent a match if certain text is found within the generated context of the match. This is useful for filtering out common false positives. You can use this flag multiple times to exclude different terms.
For example, if you are searching for the keyword "model", you might get unwanted results for "model for sale". Using the flag exclude="for sale" would prevent these matches. The text inside the quotes is case-insensitive. For single-word exclusions, quotes are not necessary (e.g., exclude=sale).
To exclude multiple terms, simply add more flags: exclude=one exclude="some phrase" exclude=three. A match will be skipped if any of the exclusion terms are found.
The include-any and include-all flags do the opposite of exclude: they require additional terms to be present for a match to occur. Use quotes for multi-word phrases (e.g., include-all="safety rating").
The include-any flag requires at least one of the specified terms to be present. For example, to find healthy recipes that involve apples or oranges, you could use: healthy recipes include-any=apple include-any=orange.
The include-all flag requires all of the specified terms to be present. For example, to find car reviews that mention both safety and ratings, you could use: car review include-all=safety include-all=rating.
You can combine these flags. If you do, a match will only occur if all of the include-all terms are found, and at least one of the include-any terms is found.
Power Users can access personalized RSS and JSON feeds of their alerts. Get your feed URLs from your account page.
The feeds are intended for use in feed readers. They are cached for a couple of minutes, so polling more often than that simply returns the same data until the cache refreshes. If you need real-time alerts for a serious automated workload, the API (available on the Ultra tier) offers webhook callbacks that push each alert to you the moment it happens, rather than requiring you to poll.
Batch size and ordering: Each request returns up to the 100 most recent alerts, newest first.
Retention: Alerts remain available in the feed for 90 days. Older alerts age out and are no longer returned.
Group Filtering: Use ?group=XXXX to filter alerts by group name:
...&group=stocks...&group=tech%20companies
Paging to older and newer alerts: Every response includes "next" and "prev" links (in the JSON feed as next_url and _prev_url; in the RSS feed as <atom:link rel="next"> and <atom:link rel="prev">). Each link carries an alert ID, and you can also construct the requests yourself:
next_id=ID returns alerts older than ID — follow the "next" link to page back through history beyond the first 100.prev_id=ID returns alerts newer than ID — this is how you fetch only the alerts that have arrived since you last checked.
The ID comes from an alert's id in the feed (the JSON id field or the RSS <guid>); you may pass either the full id or just its trailing number.
To poll efficiently for only new alerts: remember the id of the newest alert you have already processed, then pass it as prev_id on your next request. You will receive only the alerts that have arrived since, instead of re-reading the whole feed each time. Like the default view, a prev_id request also returns at most 100 alerts (the 100 closest after your id), so if a large number have accumulated, keep advancing prev_id until a request comes back empty.
Do not pass both next_id and prev_id in the same request; doing so returns an error.
The following features are exclusively available to Ultra tier users: