> For the complete documentation index, see [llms.txt](https://help.aikido.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aikido.dev/docs/docs-ja/zen-firewall/zen-features/webhooks.md).

# Webhooks

Slack と Microsoft Teams の通知に加えて、Zen イベント用の Webhook も設定できます。Webhook を作成または変更するには、 [Webhooks ページ](https://app.aikido.dev/settings/integrations/api/webhooks) .

リクエストが成功しない場合、Aikido は通知の再送信を 5 回試みます。HTTP ステータス 200 以外が返された場合、またはタイムアウトが発生した場合、そのリクエストは失敗と見なされます。 [このページ](https://apidocs.aikido.dev/reference/verirfying-webhooks) では webhook イベントの検証方法を説明します。

### Webhook イベント

現在、以下のイベントが送信されます:

<details>

<summary>攻撃が検出されました（サンプル）</summary>

{% code overflow="wrap" %}

```json
{
   "event_type": "zen.attack",
   "created_at": 1760015974,
   "payload": {
      "url": "http://app.aikido.dev/runtime/services/X/events?groupId=X&eventId=X",
      "eventId": 123,
      "attack": {
         "blocked": false,
         "kind": "sql_injection"
      },
      "request": {
         "method": "POST",
         "route":"/add",
         "ip_address": "::ffff:127.0.0.1",
         "user_agent": "Mozilla/5.0 ..."
      },
      "service": {
         "id": 1,
         "name": "Test",
         "environment": "production"
      },
      "instance":{
         "id": 1,
         "ip_address": "172.17.0.123",
         "hostname": "hostname.local"
      },
      "user": {
         "id": "123abc",
         "blocked_at": 0
      },
      "message": "Test で SQL インジェクションが検出されました"
   },
   "dispatched_at": 1760016033,
   "workspace_id": 123
}
```

{% endcode %}

</details>

<details>

<summary>攻撃の波が検出されました（サンプル）</summary>

```json
{
   "event_type": "zen.attack_wave",
   "created_at": 1760015974,
   "payload": {
      "url": "http://app.aikido.dev/runtime/services/X/events?groupId=X&eventId=X",
      "eventId": 123,
      "attack": [],
      "request": {
         "ip_address": "::ffff:127.0.0.1",
         "user_agent": "Mozilla/5.0 ..."
      },
      "service": {
         "id": 1,
         "name": "Test",
         "environment": "production"
      },
      "instance":{
         "id": 1,
         "ip_address": "172.17.0.123",
         "hostname": "hostname.local"
      },
      "user": {
         "id": "123abc",
         "blocked_at": 0
      },
      "message": "Test で攻撃の波が検出されました"
   },
   "dispatched_at": 1760016033,
   "workspace_id": 123
}
```

</details>

<details>

<summary>新しい外向き接続（サンプル）</summary>

```json
{
   "event_type": "zen.outbound.discovered",
   "created_at": 1760016813,
   "payload": {
      "hostname": "aikido.dev",
      "port": 443,
      "service": {
         "id": 123,
         "name": "Test",
         "environment": "production"
      },
      "message": "Test で新しい外向き接続が検出されました"
   },
   "timestamp": 1757599746000
}
```

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.aikido.dev/docs/docs-ja/zen-firewall/zen-features/webhooks.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.