Neynar Documentation
For user by channel
Group: Notification APIs
Use this when you need: For user by channel.
Usage
import { NeynarAPIClient, Configuration } from "@neynar/nodejs-sdk";
const client = new NeynarAPIClient(
new Configuration({ apiKey: "YOUR_NEYNAR_API_KEY" })
);
const res = await client.fetchChannelNotificationsForUser({
fid: 123, // FID of the user you you want to fetch notifications for. The response will respect this user's mutes and blocks.
channelIds: "example", // Comma separated channel_ids (find list of all channels here - https://docs.neynar.com/reference/list-all-channels)
// xNeynarExperimental: true,
// limit: 123,
// cursor: "example",
});
console.log(res);
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
fid |
number |
✅ | FID of the user you you want to fetch notifications for. The response will respect this user's mutes and blocks. |
channelIds |
string |
✅ | Comma separated channel_ids (find list of all channels here - https://docs.neynar.com/reference/list-all-channels) |
xNeynarExperimental |
boolean |
❌ | - |
limit |
number |
❌ | - |
cursor |
string |
❌ | - |
Response
Returns a RequestArgs object.
Error Handling
try {
const res = await client.fetchChannelNotificationsForUser({
fid: 123,
channelIds: "example"
});
// 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.