# History and date windows (/docs/history) Use since and until on any dated list, and see how far back each platform reaches Every list whose rows carry a date takes a window: posts, comments, replies, reviews and news articles, on every platform. This page shows how to send it, how it is applied, and how far back each platform's own search can reach. ## Use since and until Every list whose rows carry a date takes `since` and `until`: posts, comments, replies, reviews and news articles, on every platform. The window is applied to each page before it is returned, so every dated row you receive is inside it. | Parameter | Send | What happens | | --------- | ---- | ------------ | | `since` | A date (`YYYY-MM-DD`, read as midnight UTC) or an ISO 8601 timestamp | Rows published before it are left off the page. | | `until` | A date (`YYYY-MM-DD`, the whole UTC day is included) or an ISO 8601 timestamp | Rows published after it are left off the page. | ```bash title="cURL" curl "https://www.socialcrawl.dev/v1/youtube/video/comments?url=https://www.youtube.com/watch?v=dQw4w9WgXcQ&since=2025-10-07" \ -H "x-api-key: YOUR_API_KEY" ``` ## How the window is applied Lists in date order stop at `since`. On these lists `since` sets the newest-first sort when you leave it out, and the page that reaches an older row ends the walk with `pagination.stopped_at` set to `since`. Another sort value with `since` is a `400`. They are the creator feeds in [Incremental sync](/docs/pagination.md#incremental-sync) and `app_store/app-reviews` (`sort_by=most_recent`), `google_play/app-reviews` (`sort_by=newest`), `instagram/post/comments` (`sort=recent`), `linkedin/company/posts` (`sort_by=recent`), `linkedin/post/comments` (`sort_order=recent`), `naver/news/search` (`sort=date`), `naver/place/reviews` (`sort=recent`), `reddit/profile/posts` (`sort=new`), `reddit/search` (`sort=new`), `reddit/search/comments` (`sort=new`), `reddit/subreddit` (`sort=new`), `tiktok/post/comments` (`sort=recent`), `tripadvisor/reviews` (`sort_by=most_recent`), `trustpilot/reviews` (`sort=recency`), `twitter/search/tweets` (`sort=latest`), `twitter/tweet/replies` (`sort=latest`), `yelp/business/reviews` (`sort=newest`), `youtube/search/advanced` (`order=date`), `youtube/video/comments` (`order=newest`). Every other list filters each page and keeps its cursor. Comments in relevance order, keyword search and most reviews are not in date order, so an old row on page 1 says nothing about page 2. Keep following `next_cursor`; a page can come back with no rows and a cursor when every row on it was outside the window, and it says so with `data.empty_reason` set to `window_filtered`. The price does not change. Each page costs what a page of that endpoint costs, whether or not rows were left off. A row with no date is kept. A `since` or `until` that is not a date, or a `since` later than `until`, is a `400 INVALID_REQUEST` and costs nothing. So a page the window empties is still billed. To pay only when something new appears, use [Listening](/docs/engines/listening.md), which refunds a check that finds nothing, or a [Monitor](/docs/engines/monitors.md). ## Other spellings read as the window Other spellings are read as the window. `published_after`, `start_date`, `from_date` and `date_from` are applied as `since`, and `published_before`, `end_date`, `to_date` and `date_to` as `until`, on any list that does not take them under its own name. A named window (`publish_time` or `date_posted` set to `yesterday`, `this-week`, `this-month`, `last-3-months` or `last-6-months`) and a day count (`max_age_days=730`) become a `since` that far back. A list that has its own date filter keeps it: `youtube/search/advanced` still takes `published_after`, and Threads search still takes `start_date`. The other way round works too: on an endpoint with no window of its own, `since` and `until` reach the bound it takes under its own name (`start_date` on Tavily and the congress trades, `from` on news, `date_from` on the Prism reports, `startDate` on LinkedIn ads). Every rename is named in `data._warnings`, for example `"date_from was applied as since, this endpoint's name for it."`. ## Lists that refuse a date A list whose rows carry no date refuses a date. Profile lists, product lists and suggestions return `400 INVALID_REQUEST` with `error.details.reason` set to `unsupported_date_filter`, before any credit is charged, so a date key is never silently ignored. ## How far back each platform reaches This is how far back each platform's search reaches inside a [Discover](/docs/engines/discover.md) run. Each platform's own search decides how far back a window can reach. `data.platforms..window` reports what each search actually reached, with `reached: false`, `rows_outside` and `stopped_because` when it stopped before `since`. `stopped_because` is `source_ignored_window` when a source returned only posts newer than the window: none of its rows were kept, and its pages were still billed. Pages walked only to reach a past window count in the call's budget and are priced in the estimate. `data.platforms..status` is `ok`, `degraded` (some searches failed or were skipped), `failed` (every search failed), `skipped` (none ran: the platform's circuit was open or no slot was free), `unavailable` (unavailable at the source: out of quota or down) or `unsupported_country` (the platform does not serve the requested country). | Platform | Price per search page | How the window is applied | Reach | | --- | --- | --- | --- | | TikTok | 1 credit | The narrowest date bucket covering `since`, newest first; when page 1 is entirely after `until` it switches to the relevance bucket and filters locally. | A date page covers about 2 to 3 days, so a window closed up to about a week back is reached directly; up to 180 days through the relevance bucket. Older than 180 days is not reached. | | Instagram | 1 credit (hashtags 5) | Inside 90 days the relevance surface first, switching to the date surface when page 1 holds under 15% in the window; beyond 90 days the date surface. `instagram.surface=relevance` never switches. | 365 days at about 9 reels a page on the date surface. Views are empty on the date surface; `include=instagram_views` restores them. | | YouTube | 1 credit (6 with a window and `comments`) | Exact dates. | Any window. | | Reddit | 1 credit | The narrowest time bucket that misses at most 2 days, with pages. | Any window, with pages. | | X | 1 credit | Exact dates, newest first. | Any window, with pages. | | Facebook, Threads | 1 credit | Exact dates. | Any window. | | LinkedIn | 5 credits (hashtags 10) | Date order with pages; switches to relevance when page 1 is after `until`. | A page of 10 posts covers under a day for a busy keyword, so keyword search reaches only the last few days. | | Pinterest | 1 credit | Pages filtered locally. | Rows of any age arrive in relevance order, so pages add in-window rows at a steady low rate. | | Hacker News, news | 1 credit | Exact dates. | Any window; news returns at most 100 rows a call. | | Bluesky, GitHub | 1 credit | Pages filtered locally. | Rows of any date the search returns; only dated rows count in the window. | | Quora | 5 credits | Pages filtered locally. | Rows of any date the search returns; only dated rows count in the window. | | Forums | 10 credits | One fused search across forums, filtered locally. | Rows of any date the search returns; only dated rows count in the window. | | Web | 2 credits per 10 results | Exact or bucketed dates from the group's market; only dated rows count in the window. | Any window, where the page publishes a date. | | Naver blog, news, KnowledgeiN, cafe | 1 credit | The best 100 rows by relevance, then one newest-first page with a window. | By default, with a window, the top 100 plus one newest-first page; with `pages_per_platform=10`, up to the newest 1,000 rows per search. On a common word that is days, so narrower keywords reach further. Cafe rows are undated. | | Xiaohongshu (`rednote`), Douyin | 5 credits per row returned | The narrowest `published` bucket covering `since` (`half_year` for 8 to 180 days, `all` beyond), filtered locally. | 180 days on `half_year`, older rows through `all`. The bucket is sampled by relevance, so part of it falls outside a shorter window: on 17/10/2026, 2 of 5 rows of each `half_year` sample fell inside a 90-day window. Rows outside the window are dropped as `out_of_window`. Neither platform publishes view counts. | ## Next steps - [Get every row](/docs/pagination.md): Follow the cursor until a list is complete. - [Countries and languages](/docs/countries.md): Filter by country and see where a row - [Discover](/docs/engines/discover.md): Search many platforms inside one date window.