---
title: "Webhook delivery health for this org"
method: GET
path: "/orgs/{org_id}/webhooks/health"
tags: ["Webhook Notifications"]
---

# Webhook delivery health for this org

`GET /orgs/{org_id}/webhooks/health`

## Request

- Base URL: `https://api.mnemom.ai/v1`
- URL: `https://api.mnemom.ai/v1/orgs/{org_id}/webhooks/health`
- Auth: HTTP bearer

Returns active + disabled endpoint counts, 24-hour delivery counts (success / failed / total), success rate, and the top event types delivered in the last 24 hours. Useful for Status-page-style dashboards or monitoring integrations. Read-only: `owner`, `admin`, and `auditor`.

## Path parameters

- `org_id` string, required

## Response `200`

Health metrics.

- object
  - `active_endpoints` integer
  - `disabled_endpoints` integer
  - `deliveries_24h` integer
  - `success_24h` integer
  - `failed_24h` integer
  - `success_rate_24h` number
  - `top_event_types` object[]
    - `event_type` string
    - `count` integer

## Other responses

- `400`: Bad request
- `401`: Authentication required
- `403`: Forbidden
- `404`: Resource not found
- `409`: Resource conflict — the request cannot proceed because of a current state conflict (e.g., resource already exists, version mismatch, in-flight idempotency key with a different body).
- `429`: Rate-limit exceeded. The global per-IP limiter (100 requests/minute, applied to every `/v1/*` route) rejected this request. Back off until the window resets — `Retry-After` carries the cooldown in seconds and `X-RateLimit-Reset` the absolute reset time.
- `500`: Server error — request was well-formed but the server failed to fulfill it. Typically a downstream dependency (DB / RPC / external API) returned an unexpected error.

---

[API](https://skmtc.dev/mnemom/apis/mnemom-api.md) · [All operations](https://skmtc.dev/mnemom/apis/mnemom-api/llms.txt) · [OpenAPI document](https://skmtc.dev/mnemom/apis/mnemom-api/revisions/274b7a6ea182?raw)