Webhooks HTTP Servers

Dashboard Location: Network-wide > Configure > Alerts > Webhooks > HTTP Servers

## Webhooks HTTP Server Management

Webhook HTTP servers in Meraki define the destination endpoints that receive real-time alert notifications from the Meraki platform. When configured, Meraki sends HTTP POST requests containing alert data to the specified URL whenever network events occur. Each HTTP server can reference a payload template that controls the format of the data sent, enabling integration with monitoring platforms, SIEM solutions, and incident management systems. HTTP servers support shared secret authentication and can be associated with custom or built-in payload templates.

### Diagram
<div class="flex justify-center">

```d2
direction: up
style: {
  fill: transparent
}
vars: {
  d2-config: {
    theme-overrides: {
      B1: "#07182d"
      B2: "#0a60ff"
    }
    dark-theme-overrides: {
      B2: "#02c8ff"
      N7: "#07182d"
    }
  }
}

"meraki": {
  shape: sql_table
  "domains": List
}

"domains": {
  shape: sql_table
  "*organizations": List
}

"organizations": {
  shape: sql_table
  "networks": List
}

"networks": {
  shape: sql_table
  "webhooks": Dict
}

"webhooks": {
  shape: sql_table
  "http_servers": List
}

"meraki" <- "domains"
"domains" <- "organizations"
"organizations" <- "networks"
"networks" <- "webhooks": {
  source-arrowhead.shape: diamond
}

"webhooks" <- "http_servers"
"http_servers": {
  shape: sql_table
  "*name": Str
  "url": Str
  "shared_secret": Str
  "payload_template": Dict
}

"http_servers" <- "payload_template": {
  source-arrowhead.shape: diamond
}

"payload_template": {
  shape: sql_table
  "payload_template_id": Str
  "name": Str
}

Classes

webhooks (meraki.domains.organizations.networks)

Name	Type	Constraint	Mandatory	Default Value
http_servers	List	[http_servers]	No

http_servers (meraki.domains.organizations.networks.webhooks)

Name	Type	Constraint	Mandatory	Default Value
name	String	min: 1, max: 127	Yes
url	String	min: 1, max: 1024	No
shared_secret	String	min: 1, max: 1024	No
payload_template	Class	[payload_template]	No

payload_template (meraki.domains.organizations.networks.webhooks.http_servers)

Name	Type	Constraint	Mandatory	Default Value
payload_template_id	String	min: 1, max: 127	No
name	String	min: 1, max: 127	No

Examples

Example-1: The example below demonstrates configuring a webhook HTTP server for Splunk integration that references a custom payload template.

This configuration creates an HTTP server named “splunk_server” that sends webhook data to a Splunk HTTP Event Collector endpoint. The payload_template.name references a previously defined payload template (“splunk_template”) that formats the alert data for Splunk ingestion. The URL points to the Splunk HEC endpoint.

meraki:
  domains:
    - name: !env domain
      administrator:
        name: !env org_admin
      organizations:
        - name: !env org
          networks:
            - name: !env network_name
              product_types:
                - appliance
                - switch
                - wireless
              webhooks:
                http_servers:
                  - name: splunk_server
                    url: https://splunk.example.com:8088/services/collector
                    payload_template:
                      name: splunk_template

</div>