# minimumLedgerSlot

## minimumLedgerSlot RPC Method

> Returns the lowest slot that the node has information about in its ledger. This method is useful for understanding the historical data availability of a Solana node. The value may increase over time if the node is configured to purge older ledger data to manage storage requirements. This is particularly important for applications that need to query historical data, as attempting to access slots below this minimum will result in data not being available. The method provides a simple way to determine the earliest point in time for which the node can provide blockchain state information.<br>

````json
{"openapi":"3.0.3","info":{"title":"Solana RPC API - minimumLedgerSlot Method","version":"1.0.0"},"tags":[{"name":"Node Information","description":"Methods related to retrieving information about the Solana node itself,\nincluding its current state, capabilities, and data availability.\n"}],"servers":[{"url":"https://public.rpc.solanavibestation.com"},{"url":"https://basic.rpc.solanavibestation.com"},{"url":"https://ultra.rpc.solanavibestation.com"},{"url":"https://elite.rpc.solanavibestation.com"},{"url":"https://epic.rpc.solanavibestation.com"},{"url":"https://basic.swqos.solanavibestation.com"},{"url":"https://ultra.swqos.solanavibestation.com"},{"url":"https://elite.swqos.solanavibestation.com"}],"security":[{},{"AuthHeader":[]},{"URLParameter":[]}],"components":{"securitySchemes":{"AuthHeader":{"type":"apiKey","in":"header","name":"Authorization","description":"Authorization header for API key authentication.\n\n**Example:**\n```\nAuthorization: your-api-key-here\n```\n"},"URLParameter":{"type":"apiKey","in":"query","name":"api_key","description":"API key passed as a URL parameter for authentication.\n\n**Example:**\n```\nhttps://public.rpc.solanavibestation.com/?api_key=your-api-key-here\n```\n"}},"schemas":{"MinimumLedgerSlotRequest":{"type":"object","required":["jsonrpc","id","method"],"properties":{"jsonrpc":{"type":"string","description":"JSON-RPC protocol version","enum":["2.0"]},"id":{"oneOf":[{"type":"string"},{"type":"number"}],"description":"Request identifier that will be returned in the response"},"method":{"type":"string","description":"The RPC method name","enum":["minimumLedgerSlot"]},"params":{"type":"array","description":"This method takes no parameters. The params array should be empty or omitted entirely.\n","maxItems":0}}},"MinimumLedgerSlotResponse":{"type":"object","description":"RPC response containing the minimum ledger slot number","required":["jsonrpc","id"],"properties":{"jsonrpc":{"type":"string","description":"JSON-RPC protocol version","enum":["2.0"]},"id":{"oneOf":[{"type":"string"},{"type":"number"}],"description":"Request identifier matching the original request"},"result":{"type":"integer","format":"int64","description":"The lowest slot number that the node has information about in its ledger. This represents the earliest point in blockchain history for which the node can provide data. Slots below this number have been purged from the node's storage and are no longer accessible. This value may increase over time as nodes periodically clean up old data to manage storage requirements.\n","minimum":0},"error":{"$ref":"#/components/schemas/RpcError"}}},"RpcError":{"type":"object","description":"Standard JSON-RPC error object","required":["code","message"],"properties":{"code":{"type":"integer","description":"Numeric error code following JSON-RPC 2.0 specification:\n- `-32700`: Parse error\n- `-32600`: Invalid request  \n- `-32601`: Method not found\n- `-32602`: Invalid params (this method expects no parameters)\n- `-32603`: Internal error\n- `-32005`: Too Many Requests\n- `-32003`: Unauthorized\n"},"message":{"type":"string","description":"Human-readable error message"},"data":{"type":"object","description":"Additional structured error information (optional)","additionalProperties":true}}}}},"paths":{"/":{"post":{"summary":"minimumLedgerSlot RPC Method","description":"Returns the lowest slot that the node has information about in its ledger. This method is useful for understanding the historical data availability of a Solana node. The value may increase over time if the node is configured to purge older ledger data to manage storage requirements. This is particularly important for applications that need to query historical data, as attempting to access slots below this minimum will result in data not being available. The method provides a simple way to determine the earliest point in time for which the node can provide blockchain state information.\n","operationId":"minimumLedgerSlot","tags":["Node Information"],"requestBody":{"required":true,"content":{"application/json":{"schema":{"$ref":"#/components/schemas/MinimumLedgerSlotRequest"}}}},"responses":{"200":{"description":"Successful Response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/MinimumLedgerSlotResponse"}}}},"401":{"description":"Unauthorized","content":{"text/plain":{"schema":{"type":"string"}}}},"403":{"description":"Forbidden","content":{"text/plain":{"schema":{"type":"string"}}}},"429":{"description":"Too Many Requests","content":{"text/plain":{"schema":{"type":"string"}}}},"500":{"description":"Internal Server Error","content":{"text/plain":{"schema":{"type":"string"}}}}}}}}}
````