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 api docid\ ee9anjjlombmff1vx4ujw for application payment workflows, and use lnd rest, websocket, or grpc for direct lightning node operations authorized by an lnd macaroon current api reference 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 authentication 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 when to use the infrastructure api use the infrastructure api for supported hosted node management workflows such as listing and inspecting nodes for an organization creating hosted nodes when the product and organization are eligible starting, stopping, updating, or deleting nodes managing supported node settings retrieving supported certificate, macaroon, or connection material 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 infrastructure api vs lnd api the infrastructure api manages voltage hosted infrastructure it does not replace the lnd api use configuration docid 9e9fmbsr1zz4nbvl47afl , rest docid\ ccwymsz2axxdlr4lyhqpd , and grpc docid\ zf545syqrbuqiufluhlpt 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 node lifecycle and recovery treat node creation, initialization, recovery, update, stop, and delete operations as controlled infrastructure changes before automating a lifecycle operation confirm the target organization, environment, node, and bitcoin network confirm the operation and expected state transition in the current reference use a dedicated infrastructure api key owned by the correct backend system protect all node sensitive material through the current approved security workflow verify the resulting node state before continuing record the operating owner, recovery owner, and escalation path do not use historical backup upload, support macaroon, swap, initialization, or recovery examples unless the current api and security owner explicitly document that workflow access controls limit infrastructure api access to trusted operators and backend systems use separate keys for separate systems or environments where supported keep infrastructure api keys separate from payments api keys and lnd macaroons review and remove unused keys during operator changes, incident response, and production launches confirm destructive and recovery sensitive actions through the current operating runbook documentation scope 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 related pages node backed infrastructure docid\ zx2rflnnfmmh8ixlmcxbaaccess model docid\ j3t5kpxleklmfldwhdo7wnode security docid\ rlda4beej5rlbld3jm2qlmacaroons docid\ gwvwanydfdd27zrsn32pcconfiguration docid 9e9fmbsr1zz4nbvl47aflresources docid\ uldxo3 oydlivaxfda5lk