# List trending searches

Return normalized Trending Now episodes without collapsing repeated titles across distinct episodes.

- Platform: [Google Trends](https://docs.upscrape.com/docs/platforms/google_trends)
- Capability ID: `google_trends.trending.list`
- Cost: 1 credit per request
- Maximum runtime: 60 seconds
- Execute endpoint: `POST https://data.upscrape.com/execute`

## Request

Use the exact public capability ID in the shared execute envelope.

```bash
curl --request POST \
  --url https://data.upscrape.com/execute \
  --header "Authorization: Bearer YOUR_API_KEY" \
  --header "Content-Type: application/json" \
  --header "Prefer: wait=30" \
  --data '{
  "input": {
    "country": "US",
    "hours": 24,
    "limit": 25,
    "sort": "started_at"
  },
  "capability": "google_trends.trending.list"
}'
```

## Input

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `country` | `string` | Yes | Country supplied for this request. |
| `hours` | `integer` | No | Hours supplied for this request. Allowed values: `4`, `24`, `48`, `168`. |
| `include_ended` | `boolean` | No | Include ended supplied for this request. |
| `limit` | `integer` | No | Maximum number of results to return. |
| `sort` | `string` | No | Sort order for returned results. Allowed values: `relevance`, `title`, `volume`, `started_at`. |

### Example input

```json
{
  "country": "US",
  "hours": 24,
  "limit": 25,
  "sort": "started_at"
}
```

## Response

Successful output is returned in `results[0].data`. Raw platform output is intentionally open-ended and may evolve with the upstream source.

### Illustrative sample output

This redacted fixture is an example, not a fixed response schema.

```json
{
  "country": "US",
  "execution": {
    "country_verified": true,
    "duplicates_removed": 0,
    "records_observed": 321,
    "response_normalized": true,
    "transport": "[redacted:implementation_detail]",
    "upstream_status": 200
  },
  "hours": 24,
  "trends": [
    {
      "active": true,
      "growth_percent": 50,
      "id": "mlb playoff picture|2026-09-19T03:40:00Z",
      "related_queries": [
        "mlb playoff picture",
        "mlb wildcard standings",
        "al wild card standings"
      ],
      "search_volume": 1000,
      "started_at": "2026-09-19T03:40:00Z",
      "title": "mlb playoff picture"
    },
    {
      "active": true,
      "growth_percent": 100,
      "id": "swimming|2026-09-19T03:30:00Z",
      "related_queries": [
        "swimming"
      ],
      "search_volume": 200,
      "started_at": "2026-09-19T03:30:00Z",
      "title": "swimming"
    }
  ]
}
```
### Illustrative output fields

Derived from the sample above for orientation only. These fields are not a fixed response schema.

| Path | Observed type | Example |
| --- | --- | --- |
| `country` | `string` | US |
| `execution` | `object` | 6 fields |
| `execution.country_verified` | `boolean` | true |
| `execution.duplicates_removed` | `integer` | 0 |
| `execution.records_observed` | `integer` | 321 |
| `execution.response_normalized` | `boolean` | true |
| `execution.transport` | `string` | [redacted:implementation_detail] |
| `execution.upstream_status` | `integer` | 200 |
| `hours` | `integer` | 24 |
| `trends` | `array` | 2 items |
| `trends` | `array` | 2 items |

## Execution behavior

A `200` response completed inline. A `202` response was queued; poll `GET /jobs/{id}` until the job reaches `completed` or `failed`. Use an `Idempotency-Key` when retrying must not create a duplicate logical job.

## Related documentation

- [Authentication](https://docs.upscrape.com/docs/api/authentication)
- [Jobs and results](https://docs.upscrape.com/docs/api/jobs)
- [Errors and retries](https://docs.upscrape.com/docs/api/errors)
- [Idempotency](https://docs.upscrape.com/docs/api/idempotency)