Skip to content
On this page
Reference → Airnode → v0.11 → Understanding Airnode

Heartbeat (optional)

At the end of an Airnode's run (every minute), Airnode can make an HTTP POST request to a specified URL. This is both to signal that the Airnode is alive and working (useful especially right after the deployment) and also as a notification every time it runs (self-operates).

  1. Airnode gathers on-chain requests targeting the API operations it supports.

  2. The required API operation for each request is called.

  3. A response is sent to each request.

  4. Finally Airnode makes a request to the heartbeat URL (HTTP POST). This could be to an operation within the API Airnode supports or to any cloud REST endpoint such as a monitoring service.

Turn on the optional heartbeat functionality by setting all fields in the config.json section for nodeSettings.heartbeat.

      "airnodeWalletMnemonic": "<FILL_*>",
      "cloudProvider": {
        "type": "aws",
        "region": "us-east-1"
      "heartbeat": {
        "enabled": true,
        "url": "${HEARTBEAT_URL}",
        "apiKey": "${HEARTBEAT_API_KEY}"
      "httpGateway": {
        "enabled": true,
        "maxConcurrency": 20,
        "corsOrigins": []
      "httpSignedDataGateway": {
        "enabled": true,
        "maxConcurrency": 20,
        "corsOrigins": []
      "oevGateway": {
         "enabled": true,
         "maxConcurrency": 20,
         "corsOrigins": []
      "logFormat": "json",
      "logLevel": "INFO",
      "nodeVersion": "0.11.1",
      "stage": "testnet",
  • enabled: Enable/disable Airnode's heartbeat.
  • url: The URL to make the heartbeat request to.
  • apiKey: The API key to authenticate with the heartbeat URL.

Heartbeat Endpoint

The table below illustrates the parameters passed to the Heartbeat URL.


Below is an example of what is included in the request body. Note that airnode-heartbeat-api-key can be found in the request header and not the body.

  "payload": {
    "timestamp": 1661582891,
    "stage": "2209100913",
    "cloud_provider": "aws",
    "deployment_id": "aws40207f25",
    "region": "us-east-1",
    "http_gateway_url": "",
    "http_signed_data_gateway_url": "",
    "oev_gateway_url": ""
  "signature": "0x733f81fa1dffab3188e50ad66c178a22aca3a781d79a1b8daee7828cff31d1443d89efd5a2b1f40fc70953c9c5838cc8d5747374f3cf25d092331ba15b6420651c"

The method by which the heartbeat payload is generated is as follows:

  • An object is marshalled to JSON - this object contains multiple fields as shown above.
  • The Airnode's mnemonic (using the default EVM derivation path to derive a key) is used to sign the payload.
  • The payload and signature are included in a new object and marshalled to JSON.

The reason this nested JSON approach has been used is to prevent subtle inconsistencies between JSON marshallers in different languages causing the signature to not match the payload.

The airnode's public key can be recovered from this signature and be used, generally, to verify the authenticity of the payload.

The overall content to the heartbeat URL is as follows:

airnode-heartbeat-api-key:API key for heartbeat calls configured in nodeSettings.heartbeat.apiKey. Used for authentication against the heartbeat service running on URL from nodeSettings.heartbeat.url.
timestamp:This is the heartbeat timestamp.
stage:This is the deployment stage.
cloud_provider:This is the deployment cloud provider.
deployment_id:This is the deployment ID.
region:This is the deployment region.
http_gateway_url:If HTTP gateway is enabled this is the URL of the gateway you can make test HTTP calls against.
http_signed_data_gateway_url:If HTTP signed data gateway is enabled this is the URL of the gateway you can make HTTP calls against.
oev_gateway_url:If OEV gateway is enabled this is the URL of the gateway you can make HTTP calls against.
signature:This is the signature of the heartbeat payload signed with the Airnode wallet.

Released under the MIT License.