# ledger_accept

[[Source]](https://github.com/XRPLF/rippled/blob/a61ffab3f9010d8accfaa98aa3cacc7d38e74121/src/ripple/rpc/handlers/LedgerAccept.cpp)

The `ledger_accept` method forces the server to close the current-working ledger and move to the next ledger number. This method is intended for testing purposes only, and is only available when the `rippled` server is running stand-alone mode.

*The `ledger_accept` method is an [admin method](/es-es/docs/references/http-websocket-apis/admin-api-methods) that cannot be run by unprivileged users!*

### Request Format

An example of the request format:

WebSocket

```json
{
   "id": "Accept my ledger!",
   "command": "ledger_accept"
}
```

Commandline

```sh
#Syntax: ledger_accept
rippled ledger_accept
```

The request accepts no parameters.

### Response Format

An example of a successful response:


```js
{
  "id": "Accept my ledger!",
  "status": "success",
  "type": "response",
  "result": {
    "ledger_current_index": 6643240
  }
}
```

The response follows the [standard format](/docs/references/http-websocket-apis/api-conventions/response-formatting), with a successful result containing the following field:

| `Field` | Type | Description |
|  --- | --- | --- |
| `ledger_current_index` | Unsigned Integer - [Ledger Index](/docs/references/protocol/data-types/basic-data-types#ledger-index) | Ledger index of the newly created 'current' ledger |


When you close a ledger, `rippled` determines the canonical order of transactions in that ledger and replays them. This can change the outcome of transactions that were provisionally applied to the current ledger.

### Possible Errors

* Any of the [universal error types](/docs/references/http-websocket-apis/api-conventions/error-formatting#universal-errors).
* `notStandAlone` - If the `rippled` server is not currently running in stand-alone mode.