Voltage Infrastructure API

The Voltage Infrastructure API is the management interface for Voltage-hosted node infrastructure. It is separate from both the Payments API and direct LND access.

Use this API for supported organization-scoped node-management workflows. Use the Voltage Payments APIVoltage Payments API for application payment workflows, and use LND REST, WebSocket, or gRPC for direct Lightning node operations authorized by an LND macaroon.

The current production base URL is https://api.voltage.cloud.

Use the exact paths, methods, fields, and state values from the maintained Infrastructure API reference available to your organization. Availability can depend on the node product and organization configuration.

Authenticate server-side requests with an Infrastructure API key in the X-VOLTAGE-AUTH header.

Infrastructure API keys are different from Payments API keys and LND macaroons. Do not reuse one interface's authentication instructions for another.

In the current dashboard and backend, organization owners create and manage Infrastructure API keys. The dashboard allows up to five active keys, displays the Team ID needed for organization-scoped requests, and reveals a newly created key only once.

Store keys in an approved secret system, keep them out of client applications, and rotate or delete them when access changes.

Use the Infrastructure API for supported hosted-node management workflows such as:

Deployed routes are not automatically a promise that every operation is part of the supported public contract. Confirm the current method, path, schema, availability, and operating owner before automating a workflow.

The Infrastructure API manages Voltage-hosted infrastructure. It does not replace the LND API.

Use ConfigurationConfiguration, RESTREST, and GRPCGRPC when an implementation needs direct Lightning node access. Use only command-line connection instructions verified for the target node and client version.

Use the Payments API for the managed payments product. Use the Infrastructure API for Node-backed infrastructure administration.

Treat node creation, initialization, recovery, update, stop, and delete operations as controlled infrastructure changes.

Before automating a lifecycle operation:

Do not use historical backup-upload, support-macaroon, swap, initialization, or recovery examples unless the current API and security owner explicitly document that workflow.

This page is the Infrastructure API entry point for hosted-node management. Endpoint tables, request and response schemas, lifecycle state definitions, and recovery-sensitive examples should be added only after they are approved as part of the supported public contract.