Deployment Files

# secrets.env

The secrets.env file is bundled with a config.json file and contains the secrets that the respective Airnode deployments will need. All variables defined in a secrets.env file will be available in the config.json file via variable interpolation (e.g. ${VARIABLE_NAME}).

There are few pieces of data that are highly recommend to be provided via variables. The variable names shown can be adjusted to anything desired. Just be sure to change the correlating interpolation value in config.json.

Variable name config.json field name Description
AIRNODE_WALLET_MNEMONIC nodeSettings.airnodeWalletMnemonic The wallet mnemonic that will be used by the Airnode
CHAIN_PROVIDER_URL chains[].providers.<name>.url The blockchain provider url
SS_MY_API_KEY apiCredentials[].securitySchemeValue A security scheme value
HEARTBEAT_URL nodeSettings.heartbeat.url The URL to make the heartbeat request to
HEARTBEAT_API_KEY nodeSettings.heartbeat.apiKey The API key to authenticate against the heartbeat URL
HEARTBEAT_ID nodeSettings.heartbeat.id The Airnode heartbeat ID for accounting purposes
HTTP_GATEWAY_API_KEY nodeSettings.httpGateway.apiKey The API key to authenticate against the HTTP gateway

Below is an example of secrets.env.

AIRNODE_WALLET_MNEMONIC="achieve climb couple wait accident symbol spy blouse reduce foil echo label"
CHAIN_PROVIDER_URL="https://mainnet.infura.io/v3/5122f3ff104f30f21412aa38fd143d53"
SS_MY_API_KEY="FRACZKMH4F32BZ8X5uTd"

HEARTBEAT_API_KEY="d714a900-3b9e-4e4d-8eae-756ef06a8836"
HEARTBEAT_ID="916d3ec80fda"
HEARTBEAT_URL="https://your.heartbeat.service.io/airnode"

HTTP_GATEWAY_API_KEY="441ffc41-3c8b-44b9-a689-63b500fd17da"
1
2
3
4
5
6
7
8
9
Last Updated: 11/2/2021, 8:52:45 AM