This guide will walk you through the process of monitoring your validator using stakefish API. In just a few minutes, you'll learn how to check details of validator.

📘

Note:

If you're interested in checking validator rewards and annual yield, please refer to the Rewards section.

Check Validator Details

To monitor the current condition of your validator, you can use the following API endpoint (it is public):

curl -X GET "https://api.hoodi.stake.fish/v1/eth/oracle/validators?ids=VALIDATOR_INDEX_OR_PUBKEY"

Replace VALIDATOR_INDEX_OR_PUBKEY with the appropriate values based on your needs:

Example values

• Single Validator by Index: https://api.hoodi.stake.fish/v1/eth/oracle/validators?ids=1754301
• Multiple Validators by Index (max 100): https://api.hoodi.stake.fish/v1/eth/oracle/validators?ids=1754301,1754302
• Single Validator by Public Key: https://api.hoodi.stake.fish/v1/eth/oracle/validators?ids=0x8bd0438e7c38a18e0733cd7362a5af5c677e2dffa0a6af6e279322e3918832462ce5b651ca9ca8f6455196cfec74b378
• Multiple Validators by Public Key (max 50): https://api.hoodi.stake.fish/v1/eth/oracle/validators?ids=0x8bd0438e7c38a18e0733cd7362a5af5c677e2dffa0a6af6e279322e3918832462ce5b651ca9ca8f6455196cfec74b378,0xa3ee4597cd0df036691bef3cafa4d01afd0527b985c77b2655c0f23647ba49104190e39752fcb7ce45645d4057e01f65

📝

Note: You can query up to 100 validators by index or up to 50 by public key per request. The lower limit for public keys reflects the larger payload size of pubkey strings.

Example Response:

After sending the GET request, you'll receive a response similar to the following:

{
  "results": [
    {
      "pubkey": "0x8bd0438e7c38a18e0733cd7362a5af5c677e2dffa0a6af6e279322e3918832462ce5b651ca9ca8f6455196cfec74b378",
      "index": 1754301,
      "activatedAt": "2024-07-14T17:39:12",
      "activationEligibilityEpoch": "64675",
      "activationEpoch": "65303",
      "exitEpoch": "76723",
      "withdrawableEpoch": "76979",
      "effectiveBalance": "32000000000000000000",
      "status": "active_exiting",
      "updatedAtEpoch": "76722",
      "cluster": "entities",
      "balance": "32004476654000000000",
      "withdrawalCredentials": "0x0100000000000000000000000c246467608374f2ad145cba7ce16c2a826003d1",
      "node": "hoodi-lighthouse0",
      "owner": "0xd5e73f9199E67b6Ff8DFACE1767A1BDAdf1A7242",
      "eigenLayer": {
        "isUsingEigenPod": true
      },
      "blsToEthInProgress": false,
      "totalDepositValue": "32000000000000000000",
      "depositedAt": "2024-07-11T06:40:24",
      "nft": null,
      "estimatedActivationEpoch": null,
      "estimatedActivationTime": null,
      "estimatedPositionInQueue": null
    }
  ],
  "totalItems": 1
}

Understanding the Response

This response provides detailed information about your validator, including:

• pubkey: The public key of the validator.
• index: The validator's index number.
• activatedAt: The timestamp when the validator was activated.
• status: The current status of the validator (e.g., active_exiting).
• withdrawalCredentials: The address where withdrawn funds will be sent.
• balance: The current balance of the validator.
• effectiveBalance: The validator's effective balance in wei (e.g., "32000000000000000000" = 32 ETH). Note: The Ethereum consensus layer natively uses gwei, but this API returns the value in wei for consistency.
• node: The node the validator is associated with.
• eigenLayer: Information about the validator's use of EigenPod, if applicable.
• blsToEthInProgress: (Legacy) Indicates whether a BLS-to-execution credential conversion is in progress. This only applies to validators originally created with BLS (0x00) withdrawal credentials before the Shapella upgrade (April 2023). New validators are created with execution credentials directly and will always show false.

For a detailed explanation of every field, refer to the API Specifications.