## Relevant followers

**Group:** Channel APIs

Use this when you need: **Relevant followers**.

## Usage

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

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

const res = await client.fetchRelevantFollowersForAChannel({
  id: "example", // Channel ID being queried
  viewerFid: 123, // The FID of the user to customize this response for. Providing this will also return a list of followers that respects this user’s mutes and blocks and includes `viewer_context`.
  // xNeynarExperimental: true,
});
console.log(res);
```

## Parameters

| Parameter           | Type     | Required | Description                                                                                                       |
| ------------------- | -------- | -------- | --------------------------------------------------------------------------------------------------------------- |
| `id`                | `string` | ✅       | Channel ID being queried                                                                                       |
| `viewerFid`        | `number` | ✅       | The FID of the user to customize this response for. Providing this will also return a list of followers that respects this user’s mutes and blocks and includes `viewer_context`. |
| `xNeynarExperimental` | `boolean` | ❌     | -                                                                                                             |

## Response

Returns a `RequestArgs` object.

## Error Handling

```javascript
try {
  const res = await client.fetchRelevantFollowersForAChannel({
    id: "example",
    viewerFid: 123
  });
  // 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.