# getIdentity

> Returns the identity public key of the node that answers the request.

Source: https://docs.constant-k.com/rpc/http/getidentity/

`getIdentity` returns the identity public key of the node handling the call. Every validator and RPC-only node has an identity keypair used to sign gossip messages, votes and, for a leader, blocks; this exposes the public half of it.

Diagnostic uses include matching a response to a specific node in a fleet, or cross-referencing against `getClusterNodes` or `getVoteAccounts`.

- Transport: HTTP, JSON-RPC 2.0 `POST` to `https://rpc-newyork.constant-k.com/?api-key=YOUR_API_KEY` (New York) or `https://rpc-frankfurt.constant-k.com/?api-key=YOUR_API_KEY` (Frankfurt) or `https://rpc-amsterdam.constant-k.com/?api-key=YOUR_API_KEY` (Amsterdam). The key also works as an `x-api-key` header.
- Category: Network & Cluster
- Availability: All plans
- Rate limits: Free 5/s · Operator 50/s · Blade Runner 200/s · Nexus 500/s

## Parameters

None.

## Result

- `result` (object, optional): An object containing the node's identity public key.
  - `identity` (string, required): Base-58 encoded public key of the responding node's identity account.

## Example: Get node identity

Request:

```bash
curl "https://rpc-newyork.constant-k.com/?api-key=YOUR_API_KEY" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{ "jsonrpc": "2.0", "id": 1, "method": "getIdentity" }'
```

Response:

```json
{
  "jsonrpc": "2.0",
  "result": {
    "identity": "7bheQjnMgS4q4MuMkd8gSpAudDGkmtiQYZZGxxecHtgh"
  },
  "id": 1
}
```

## Notes

- constant-k serves requests from more than one backend node, so repeated calls can return different `identity` values.