# Time Range & News History

> [!WARNING]
> The Web Content API is **deprecated**. Use the [News, Blogs & Forums APIs](news-blogs-forums-overview) instead - same content, one endpoint per content type, and where new features land.

## Default window

With no time parameter, the API returns posts crawled in the **last 3 days**.

## The `ts` parameter

`ts` is a Unix timestamp in **milliseconds**. The API returns posts crawled at or after `ts`:

```bash
&ts=1748736000000
```

`ts` is also how pagination walks backward in time - the `next` URL sets it for you.

## News history (older than 31 days)

Going back more than 31 days is a **premium** feature that consumes credits. Enable it explicitly:

```bash
&allowNewsHistory=true
```

Without `allowNewsHistory=true`, a `ts` older than 31 days is clamped to the last 3 days and the response includes a warning.

## Credit cost by time depth

Each call costs credits based on how far back `ts` reaches. The deeper into history, the more credits per call:

| How far back `ts` reaches | Credits per call |
| --- | --- |
| Last 31 days | 1 |
| 31 days - 3 months | 2 |
| 3 - 6 months | 3 |
| Older than 6 months | 4 |

`requestsLeft` in each response reflects the credits remaining after this cost.

> [!WARNING]
> News history beyond 31 days uses credits, and a single deep-history call can cost up to 4 credits. Only set `allowNewsHistory=true` when you intend to query the archive window.