## Trending feeds

**Group:** Feed APIs

Use this when you need: **Trending feeds**.

## Usage

```javascript
import { NeynarAPIClient, Configuration } from "@neynar/nodejs-sdk";

const client = new NeynarAPIClient(
  new Configuration({ apiKey: "YOUR_NEYNAR_API_KEY" })
);

const res = await client.fetchTrendingFeed({
  // xNeynarExperimental: true,
  // limit: 123,
  // cursor: "example",
  // viewerFid: 123,
  // timeWindow: "value",
  // channelId: "example",
  // parentUrl: "example",
  // provider: "value",
});
console.log(res);
```

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `xNeynarExperimental` | `boolean` | ❌ | - |
| `limit` | `number` | ❌ | - |
| `cursor` | `string` | ❌ | - |
| `viewerFid` | `number` | ❌ | - |
| `timeWindow` | `FetchTrendingFeedTimeWindowEnum` | ❌ | - |
| `channelId` | `string` | ❌ | - |
| `parentUrl` | `string` | ❌ | - |
| `provider` | `FetchTrendingFeedProviderEnum` | ❌ | - |

## Response

Returns a `RequestArgs` object.

## Error Handling

```javascript
try {
  const res = await client.fetchTrendingFeed({ /* required fields */ });
  // use res
} catch (err) {
  // Axios/HTTP errors, invalid params, auth issues, etc.
  console.error(err);
}
```

## Tips

- Provide a **viewerFid** when supported to respect mutes/blocks and include `viewer_context`.
- Keep requests scoped (e.g., use `limit`) to improve latency.
- Cache results where sensible.