Quick Reference
| Method | Parameters | Description |
|---|---|---|
status | none | Returns general status of a given node and validator set |
network_info | none | Returns current state of node network connections |
validators | epoch_id OR [null] | Returns active validators on the network |
Node Status
Returns general status of a given node (sync status, nearcore node version, protocol version, etc.), and the current set of validators.status[]Network Info
Returns the current state of node network connections (active peers, transmitted data, etc.)network_infonone
Validation Status
Queries active validators on the network returning details and the state of validation on the blockchain.validators[null] for current validators, or {"epoch_id": "..."} for specific epochYou can obtain the
epoch_id from a block that belongs to a specific epoch. If you want to retrieve the current list of validators, pass null as the parameter. Additionally, you can query validators for past epochs by providing the epoch_id of the desired past epoch.Query current validators
Query by epoch_id
Error Handling
Common Error Types
| Error Code | Description | Solution |
|---|---|---|
UnknownEpoch | Epoch ID not found | Use a valid epoch ID from existing blocks |
InvalidAccount | Invalid account format | Use valid account ID format (e.g., account.near) |
RequestTimeout | Request timed out | Retry the request or use a different RPC endpoint |
InternalError | Server-side error | Retry the request after a short delay |
MethodNotFound | Invalid method name | Check method spelling and API version |
Best Practices
- Cache validator data: Validator information changes infrequently, consider caching for several minutes
- Use specific queries: Request only the data you need to minimize response size
- Monitor network health: Use
statusendpoint to check node sync status before other operations