Skip to main content
Version: development

Reload signer keys asynchronously

POST 
/reload

Reloads signer keys asynchronously in the background. This endpoint is used after adding, removing, or modifying keystore files to make Web3Signer aware of the changes without restarting.

The reload operation:

  • Scans all configured keystore directories and remote vaults
  • Loads valid signer configurations
  • Logs warnings for any invalid configurations (malformed files, invalid keys, etc.)
  • Makes successfully loaded signers available for signing operations
  • Returns immediately with 202 Accepted while processing continues in the background

Important notes:

  • Only one reload operation can run at a time (subsequent requests return 409 Conflict)
  • Individual signer loading failures do not cause the entire reload to fail
  • Use GET /reload to check status and error counts
  • Successfully loaded signers are available even if some configurations fail

Not used by validator clients - this is an administrative endpoint for node operators.

Responses​

Reload request accepted and is running in the background

Last updated on by bgravenorst