---
title: "Retry Event Delivery"
method: POST
path: "/retry"
tags: ["Retry"]
---

# Retry Event Delivery

`POST /retry`

Triggers a retry for delivering an event to a destination. The event must exist and the destination must be enabled and match the event's topic.

When authenticated with a Tenant JWT, only events belonging to that tenant can be retried.
When authenticated with Admin API Key, events from any tenant can be retried.

## Request body

- RetryRequest — Request body for retrying event delivery to a destination.
  - `event_id` string, required — The ID of the event to retry.
  - `destination_id` string, required — The ID of the destination to deliver to.

## Response `202`

Retry accepted for processing.

- SuccessResponse
  - `success` boolean

## Other responses

- `400` — Bad request. This can happen when: - The destination is disabled - The destination does not match the event's topic
- `401` — Missing or invalid authentication credentials.
- `404` — Requested resource not found.
- `500` — Unexpected server error.

## Changes

- **2026-04-30** `4e68e64777ea` — 2 info
  - api tag `Retry` added
  - api tag `Attempts` removed
- **2026-02-20** `c36d2dacd201` — 4 info
  - added the media type `application/json` for the response with the status `404`
  - added the non-success response with the status `401`
  - added the non-success response with the status `500`
  - removed the non-success response with the status `422`
- **2026-02-02** `f718a615d1be` — 1 info
  - endpoint added

[Change history](https://skmtc.dev/hookdeck/apis/outpost-api/changes/retry/post.md)

---

[API](https://skmtc.dev/hookdeck/apis/outpost-api.md) · [All operations](https://skmtc.dev/hookdeck/apis/outpost-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/hookdeck/outpost-api/revisions/506c7bcee34b/schema)