---
title: "redriveOutboundDlqMessages"
method: POST
path: "/v1/integrations/{integrationId}/outbound/messages/dlq/redrive"
tags: ["integrations"]
---

# redriveOutboundDlqMessages

`POST /v1/integrations/{integrationId}/outbound/messages/dlq/redrive`

Redrive selected dead-lettered messages back into the live stream.
Operator endpoint — requires the `integration:manage` grant.
A redriven message is re-enqueued at the tail with a new id and
sequence — it is delivered out of its original per-entity order (the
stream has moved on); this is inherent to redrive and matches SQS DLQ
semantics. The redriven copy starts with zero delivery attempts and a
fresh retention window; the original DLQ entry is removed. Per-id
results report `redriven` or `not_found` (unknown ids, or entries
concurrently redriven/expired).

## Path parameters

- `integrationId` string, uuid, required

## Request body

- RedriveOutboundDlqRequest
  - `ids` string[], required — Message ids (msg_…) of the DLQ entries to redrive

## Response `200`

Per-id redrive results

- RedriveOutboundDlqResponse
  - `results` RedriveOutboundDlqResult[], required — Per-id redrive outcome, input order preserved
    - `id` string, required — The requested message id
    - `status` 'redriven' | 'not_found', required — Outcome — `redriven` re-enqueued at the tail; `not_found` for unknown ids or entries concurrently redriven/expired

## Other responses

- `400` — Bad request
- `401` — Unauthorized request
- `403` — Forbidden - insufficient permissions
- `404` — Resource not found
- `500` — Internal Server Error

---

[API](https://skmtc.net/epilot/apis/integration-toolkit-api.md) · [All operations](https://skmtc.net/epilot/apis/integration-toolkit-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/epilot/integration-toolkit-api/revisions/c24837d75096/schema)