# getSlotLeader

> Returns the identity of the current slot leader.

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

`getSlotLeader` returns the validator leading the current slot, the one responsible for producing its block. It reads from the same leader schedule `getLeaderSchedule` exposes in bulk.

- 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: Slots & Epochs
- Availability: All plans
- Rate limits: Free 5/s · Operator 50/s · Blade Runner 200/s · Nexus 500/s

## Parameters

`params` is a positional JSON array, in this order:

- `config` (object, optional): Optional configuration.
  - `commitment` (string, optional, one of `finalized`, `confirmed`, `processed`, default `"finalized"`): Bank state to compute the current slot (and thus its leader) from.
  - `minContextSlot` (integer, optional): Minimum slot the node must have processed before answering.

## Result

- `result` (string, optional): The current slot leader's identity, base-58 encoded.

## Example: Get the current slot leader

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": "getSlotLeader", "params": [] }'
```

Response:

```json
{
  "jsonrpc": "2.0",
  "result": "A1Jj54VoGhvqk7DRykoRNcKETJ7jyPHUKBgNQbT6bADw",
  "id": 1
}
```

## Notes

- The leader changes roughly every 4 slots, about 1.6 seconds, so a cached value goes stale almost immediately.
- `getSlotLeaders` provides a forward-looking view (who leads the next N slots), instead of polling this repeatedly.