Use the Daily.dev monitoring endpoint to track developer posts on Daily.dev. Supports multiple search modes including keyword search, tag-based feeds, smart recommendations, and most-discussed posts.
How it works
- Create a saved search via
POST /v1/searches/dailydev/posts with your keywords and optional filters
- Trigify checks Daily.dev on your configured frequency (
DAILY, WEEKLY, MONTHLY, or QUARTERLY; HOURLY is available on Enterprise and Custom plans only)
- New posts matching your criteria appear in your search results with author, tags, engagement metrics, and content
- Optionally trigger workflows on new posts for alerts, enrichment, or integrations
Supported filters
| Field | Type | Required | Description |
|---|
name | string | Yes | A descriptive name for your saved search |
keywords | string[] | No | Keywords to search for (OR logic). Required for keyword-search and smart-recommendations modes |
keywords_and | string[] | No | All of these keywords must appear (AND logic) |
keywords_not | string[] | No | Exclude posts containing these keywords |
tags | string[] | No | Daily.dev tags to follow |
tags_block | string[] | No | Daily.dev tags to block |
sources_follow | string[] | No | Daily.dev source handles to follow |
sources_block | string[] | No | Daily.dev source handles to block |
search_mode | string | No | Search mode (see below). Default: keyword-search |
source_id | string | No | Daily.dev source ID (required for source-based-feed mode) |
order_by | string | No | Sort order: DATE, UPVOTES, DOWNVOTES, COMMENTS, CLICKS |
min_upvotes | number | No | Minimum upvotes filter |
min_views | number | No | Minimum views filter |
disable_engagement_filter | boolean | No | Disable the default engagement quality filter |
blocked_words | string[] | No | Words to filter from results |
blocked_content_types | string[] | No | Content types to block (e.g. video) |
discussed_period | number | No | Discussion period in days (most-discussed mode only) |
time_frame | string | No | How far back to search: past-24h, past-week, past-month, past-year, all-time |
max_results | number | No | Maximum posts to return per run (default: 50) |
frequency | string | No | How often to check: DAILY, WEEKLY, MONTHLY, QUARTERLY; HOURLY is Enterprise/Custom only |
Search modes
| Mode | Description |
|---|
keyword-search | Default. Search posts by keywords |
smart-recommendations | AI-powered recommendations based on your keywords |
tag-based-feed | Filter posts by Daily.dev tags (use tags / tags_block) |
source-based-feed | Filter posts by a specific source (requires source_id) |
popular-by-tags | Most popular posts filtered by tags |
most-discussed | Most discussed posts (use discussed_period to set the window) |
Create a Daily.dev search
curl -X POST https://api.trigify.io/v1/searches/dailydev/posts \
-H "x-api-key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"name": "AI Developer Tools",
"keywords": ["Claude Code", "Cursor", "AI coding"],
"keywords_not": ["hiring"],
"tags": ["ai", "developer-tools"],
"search_mode": "keyword-search",
"order_by": "DATE",
"time_frame": "past-week",
"frequency": "DAILY"
}'
Response
GET /v1/searches/{id}/results returns Daily.dev posts in Trigify’s standard search result shape:
| Field | Description |
|---|
id | Result identifier |
source | Always dailydev for Daily.dev results |
author.name | Post author’s display name |
author.username | Post author’s Daily.dev username |
content.text | Post summary or excerpt |
content.url | Link to the original post |
content.image | Post thumbnail image URL |
content.tags | Array of Daily.dev tags |
engagement.upvotes | Number of upvotes |
engagement.comments | Number of comments |
published_at | When the post was published |
collected_at | When the API returned the result |
For the full shared response contract, see Get Search Results.
Example: Monitor popular AI posts
curl -X POST https://api.trigify.io/v1/searches/dailydev/posts \
-H "x-api-key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"name": "Popular AI posts",
"keywords": ["artificial intelligence", "machine learning"],
"search_mode": "popular-by-tags",
"tags": ["ai", "machine-learning"],
"min_upvotes": 10,
"time_frame": "past-week",
"frequency": "DAILY"
}'
Preview your filters
Before committing to a saved search, POST the exact same body to POST /v1/searches/dailydev/posts/preview to see a sample of matching posts. Useful for validating tag / keyword / search-mode combinations before spending a credit.
curl -X POST https://api.trigify.io/v1/searches/dailydev/posts/preview \
-H "x-api-key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"name": "AI tooling trends",
"keywords": ["ai", "agents"],
"tags": ["machine-learning"],
"search_mode": "keyword-search",
"max_results": 10
}'
Response shape mirrors GET /v1/searches/{id}/results plus a meta block with count, total_available, and monitoring_type.
Preview is free — no credit charged. Once you’re happy, POST the same body to /v1/searches/dailydev/posts to commit the saved search. Note that the custom-feed search mode is not supported by preview because it requires an OAuth integration; use one of the other modes when previewing.
Credit Usage
- 1 credit per search created
- Previewing filters via
POST /v1/searches/dailydev/posts/preview is free
- Retrieving results via
GET /v1/searches/{id}/results is free
- Updating or deleting a search is free
- Subsequent runs on the configured frequency do not consume additional credits for search creation
Deprecated unified endpoint
The previous approach of sending POST /v1/searches with monitoring_type: "dailydev-posts" inside a nested query object still works but is deprecated. Use POST /v1/searches/dailydev/posts with a flat request body instead. The unified endpoint will be removed in a future release.
Notes
- Keywords use OR logic by default. Use
keywords_and for AND logic
- Use
keywords_not to exclude irrelevant results
- The
search_mode defaults to keyword-search if not specified
source-based-feed mode requires the source_id field
most-discussed mode supports discussed_period to control the time window
- The engagement quality filter is enabled by default; set
disable_engagement_filter: true to include all posts
HOURLY frequency requires an Enterprise or Custom plan
job_titles filter is not applicable for Daily.dev searches