# Admin API Methods

Administer a `rippled` server using these admin API methods. Admin methods are meant only for trusted personnel in charge of keeping the server operational. Admin methods include commands for managing, monitoring, and debugging the server.

Admin commands are available only if you connect to `rippled` on a host and port that the `rippled.cfg` file identifies as admin. By default, the commandline client uses an admin connection. For more information on connecting to `rippled`, see [Getting Started with the `rippled` API](/es-es/docs/tutorials/http-websocket-apis/build-apps/get-started).

## [Key Generation Methods](/es-es/docs/references/http-websocket-apis/admin-api-methods/key-generation-methods)

Use these methods to generate and manage keys.

* **[`validation_create`](/es-es/docs/references/http-websocket-apis/admin-api-methods/key-generation-methods/validation_create)** - Generate formatted for `rippled` node key pair. (Validators should use [tokens](/es-es/docs/infrastructure/configuration/server-modes/run-rippled-as-a-validator) instead of keys generated by this method.)
* **[`wallet_propose`](/es-es/docs/references/http-websocket-apis/admin-api-methods/key-generation-methods/wallet_propose)** - Generate keys for a new account.


## [Logging and Data Management Methods](/es-es/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods)

Use these methods to manage log levels and other data, such as ledgers.

* **[`can_delete`](/es-es/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/can_delete)** - Allow online deletion of ledgers up to a specific ledger.
* **[`ledger_cleaner`](/es-es/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/ledger_cleaner)** - Configure the ledger cleaner service to check for corrupted data.
* **[`ledger_request`](/es-es/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/ledger_request)** - Query a peer server for a specific ledger version.
* **[`log_level`](/es-es/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/log_level)** - Get or modify log verbosity.
* **[`logrotate`](/es-es/docs/references/http-websocket-apis/admin-api-methods/logging-and-data-management-methods/logrotate)** - Reopen the log file.


## [Server Control Methods](/es-es/docs/references/http-websocket-apis/admin-api-methods/server-control-methods)

Use these methods to manage the `rippled` server.

* **[`ledger_accept`](/es-es/docs/references/http-websocket-apis/admin-api-methods/server-control-methods/ledger_accept)** - Close and advance the ledger in stand-alone mode.
* **[`stop`](/es-es/docs/references/http-websocket-apis/admin-api-methods/server-control-methods/stop)** - Shut down the `rippled` server.


## [Signing Methods](/es-es/docs/references/http-websocket-apis/admin-api-methods/signing-methods)

Use these methods to sign transactions.

* **[`sign`](/es-es/docs/references/http-websocket-apis/admin-api-methods/signing-methods/sign)** - Cryptographically sign a transaction.
* **[`sign_for`](/es-es/docs/references/http-websocket-apis/admin-api-methods/signing-methods/sign_for)** - Contribute to a multi-signature.
* **[`channel_authorize`](/es-es/docs/references/http-websocket-apis/public-api-methods/payment-channel-methods/channel_authorize)** - Sign a claim for money from a payment channel.


By default, these methods are [admin-only](/es-es/docs/tutorials/http-websocket-apis/build-apps/get-started#admin-access). They can be used as public methods if the server admin has [enabled public signing](/es-es/docs/infrastructure/configuration/enable-public-signing).

## [Peer Management Methods](/es-es/docs/references/http-websocket-apis/admin-api-methods/peer-management-methods)

Use these methods to manage the server's connections in the peer-to-peer XRP Ledger network.

* **[`connect`](/es-es/docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/connect)** - Force the `rippled` server to connect to a specific peer.
* **[`peer_reservations_add`](/es-es/docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_add)** - Add or update a reserved slot for a specific peer.
* **[`peer_reservations_del`](/es-es/docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_del)** - Remove a reserved slot for a specific peer.
* **[`peer_reservations_list`](/es-es/docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/peer_reservations_list)** - List reserved slots for specific peers.
* **[`peers`](/es-es/docs/references/http-websocket-apis/admin-api-methods/peer-management-methods/peers)** - Get information about the peer servers connected.


## [Status and Debugging Methods](/es-es/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods)

Use these methods to check the status of the network and server.

* **[`consensus_info`](/es-es/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/consensus_info)** - Get information about the state of consensus as it happens.
* **[`feature`](/es-es/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/feature)** - Get information about protocol amendments.
* **[`fetch_info`](/es-es/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/fetch_info)** - Get information about the server's sync with the network.
* **[`get_counts`](/es-es/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/get_counts)** - Get statistics about the server's internals and memory usage.
* **[`manifest`](/es-es/docs/references/http-websocket-apis/public-api-methods/server-info-methods/manifest)** - Get the latest public key information about a known validator.
* **[`print`](/es-es/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/print)** - Get information about internal subsystems.
* **[`validator_info`](/es-es/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validator_info)** - Get information about the server's validator settings, if configured as a validator.
* **[`validator_list_sites`](/es-es/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validator_list_sites)** - Get information about sites that publish validator lists.
* **[`validators`](/es-es/docs/references/http-websocket-apis/admin-api-methods/status-and-debugging-methods/validators)** - Get information about the current validators.


## Deprecated Methods

The following admin commands are deprecated and either have been removed, or may be removed without further notice:

* `ledger_header` - Use the [ledger method](/docs/references/http-websocket-apis/public-api-methods/ledger-methods/ledger) instead.
* `unl_add`, `unl_delete`, `unl_list`, `unl_load`, `unl_network`, `unl_reset`, `unl_score` - Use the `validators.txt` config file for UNL management instead.
* `wallet_seed` - Use the [wallet_propose method](/docs/references/http-websocket-apis/admin-api-methods/key-generation-methods/wallet_propose) instead.
* `validation_seed` - Use the config file and `validator-keys-tool` for managing your seed instead.