---
title: "Retry Alert Attempt"
method: POST
path: "/api/v2/alert-attempts/retry"
tags: ["Alerts", "Enterprise"]
---

# Retry Alert Attempt

`POST /api/v2/alert-attempts/retry`

Manually re-queues an existing alert delivery attempt. The composite key
in the request body identifies the specific attempt (alert, event, channel/webhook) to retry. The attempt is ignored
when the attempt has already succeeded.

## Request body

- object — Request body for manually re-queueing an alert delivery attempt. The supplied composite key identifies the row to retry; the handler is a no-op when the attempt has already succeeded (`succeeded_at IS NOT NULL`).
  - `alert_id` string, uuid, required
  - `channel_id` string, uuid, required
  - `event_id` string, uuid, required

## Response `200`

OK

- object
  - `data` object
    - `alert_attempt` ModelAlertAttempt — System-generated delivery attempt for a single `(alert, channel, event)` tuple. Read-only via the API. Identity is the composite key `(alert_id, channel_id, event_id)`.
      - `alert_id` string, uuid
      - `channel_id` string, uuid
      - `event_id` string, uuid
      - `created_at` string, date-time
      - `succeeded_at` string, date-time, nullable — An RFC-3339 formatted string
      - `last_status_code` integer, nullable
      - `last_error` string, nullable
      - `attempts` integer — Total dispatch attempts fired.
      - `next_attempt_at` string, date-time, nullable — An RFC-3339 formatted string

## Other responses

- `400` — **Bad Request** This could be due to one of the following reasons: - JSON payload is missing or malformed - Path or query parameters are missing or invalid/malformed - The data sent is not valid (ex- sending a `string` in an `integer` field)
- `401` — **Unauthorized** This endpoint failed an authentication requirement. Either the client tried to access a protected endpoint without being authenticated, or an auth validation failed (ex- invalid credentials or expired token).
- `403` — **Forbidden** This is most commonly caused by an authenticated client trying to access a resource that it does not have permission for.
- `404` — **Not Found** This error typically comes from operations where a valid ID was passed to the request to look up an entity but the entity could not be found.
- `429` — **Too Many Requests** The client has sent too many requests within a certain time window and tripped the rate limiting middleware.
- `500` — **Internal Server Error** This is usually the result of either an unexpected database or application error. The client may try modifying or resending the request, but the error is likely not related to the client doing something wrong.

## Changes

- **2026-08-25** `e34679d9b779` — 1 info
  - endpoint added

[Change history](https://skmtc.dev/specterops/apis/bloodhound-api/changes/api/v2/alert-attempts/retry/post.md)

---

[API](https://skmtc.dev/specterops/apis/bloodhound-api.md) · [All operations](https://skmtc.dev/specterops/apis/bloodhound-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/specterops/bloodhound-api/revisions/6d4b33f1714e/schema)