# getHighestSnapshotSlot

> Returns the highest full and incremental snapshot slots the node has generated.

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

`getHighestSnapshotSlot` reports the most recent slots the node has a full snapshot and an incremental snapshot at. Snapshots let a node bootstrap quickly instead of replaying the ledger from genesis.

This is mainly an operator check on the node's snapshot pipeline, not something application code typically needs.

- 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

None.

## Result

- `result` (object, optional): The highest full and incremental snapshot slots.
  - `full` (integer, required): Slot of the highest full snapshot.
  - `incremental` (integer | null, optional): Slot of the highest incremental snapshot built on top of `full`, or null if none exists yet.

## Example: Get the node's highest snapshot slots

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": "getHighestSnapshotSlot" }'
```

Response:

```json
{
  "jsonrpc": "2.0",
  "result": {
    "full": 447858864,
    "incremental": 447946432
  },
  "id": 1
}
```

## Notes

- Returns a JSON-RPC error (`-32008`, no snapshot) instead of a result if the node has not generated a snapshot yet.
- `incremental` builds forward from `full` and is typically more recent, since incremental snapshots are cheap to produce often while full snapshots are periodic and expensive.