> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neynar.com/llms.txt
> Use this file to discover all available pages before exploring further.

# fetchRelevantFungibleOwners

Relevant owners

> **Group:** Onchain APIs

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

## Usage

```ts theme={"system"}
import { NeynarAPIClient, Configuration } from "@neynar/nodejs-sdk";

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

const res = await client.fetchRelevantFungibleOwners({
  contractAddress: "example", // Contract address of the fungible asset (Ethereum or Solana)
  network: "value", // Network of the fungible asset.
  // viewerFid: 123, 
});
console.log(res);
```

## Parameters

| Parameter         | Type                                     | Required | Description                                                 |
| ----------------- | ---------------------------------------- | :------: | ----------------------------------------------------------- |
| `contractAddress` | `string`                                 |     ✅    | Contract address of the fungible asset (Ethereum or Solana) |
| `network`         | `FetchRelevantFungibleOwnersNetworkEnum` |     ✅    | Network of the fungible asset.                              |
| `viewerFid`       | `number`                                 |     ❌    | -                                                           |

## Response

Returns a `RequestArgs` object.

## Error Handling

```ts theme={"system"}
try {
  const res = await client.fetchRelevantFungibleOwners({
    contractAddress: "example",
    network: "value"
  });
  // use res
} catch (err) {
  // Axios/HTTP errors, invalid params, auth issues, etc.
  console.error(err);
}
```

## Related API Reference

📖 **API Reference:** [fetchRelevantFungibleOwners](/reference/fetch-relevant-fungible-owners)

For detailed information about the HTTP endpoint, request/response schemas, and additional examples, see the complete API documentation.

## 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.