> ## Documentation Index
> Fetch the complete documentation index at: https://docs.portalhq.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Retry an alert webhook delivery event

> Manually retry the delivery of a single alert webhook event. The event's
status is set to `REPLAYING` and a one-shot delivery attempt is scheduled
on a dedicated retry queue. On completion, the event moves to `DELIVERED`
(2XX response) or `FAILED` (non-2XX response or timeout).

**Manual retries replace the automatic retry loop.** If the target event
is still `PENDING`, retrying it removes it from the normal automatic retry
flow — the manual retry becomes the only remaining attempt. See
[Delivery event lifecycle](/resources/alert-webhooks#delivery-event-lifecycle)
for the full state machine.




## OpenAPI

````yaml /openapi/custodian-api.yaml post /custodians/me/alerts/webhooks/{alertWebhookId}/delivery-events/{deliveryEventId}/retries
openapi: 3.1.0
info:
  title: Portal Custodian API
  version: '3.0'
  description: >
    The Portal Custodian API provides endpoints for managing clients, building
    transactions,

    retrieving wallet data, managing delegations, alert webhooks, and gas
    sponsorship.

    All endpoints require authentication via a Portal API Key (also known as a
    Custodian API Key)

    passed as a Bearer token.


    ## Base URL

    `https://api.portalhq.io/api/v3`


    ## Authentication

    Include your Portal API Key as a Bearer token in the `Authorization` header
    of every request.


    ## Chain ID Format

    Chain parameters use either friendly names (e.g. `ethereum`, `solana`) or
    CAIP-2 format

    (e.g. `eip155:1`, `solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp`). When using
    CAIP-2 format

    in URLs, ensure the colon is URI-encoded (`%3A`).
servers:
  - url: https://api.portalhq.io/api/v3
    description: Production
security:
  - bearerAuth: []
tags:
  - name: Clients
    description: Create and manage Portal clients
  - name: Transactions
    description: Build and evaluate blockchain transactions
  - name: Wallet Metadata
    description: Retrieve wallet balances and NFTs
  - name: Wallet Shares
    description: Manage backup shares and wallet ejection
  - name: Delegations
    description: Manage token delegations and delegated transfers
  - name: Session Keys
    description: Build and send EIP-7702 session key user operations
  - name: Alert Webhooks
    description: Manage alert webhooks, external addresses, and replay failed events
  - name: Gas Sponsorship
    description: View and manage gas sponsorship across chains
paths:
  /custodians/me/alerts/webhooks/{alertWebhookId}/delivery-events/{deliveryEventId}/retries:
    post:
      tags:
        - Alert Webhooks
      summary: Retry an alert webhook delivery event
      description: >
        Manually retry the delivery of a single alert webhook event. The event's

        status is set to `REPLAYING` and a one-shot delivery attempt is
        scheduled

        on a dedicated retry queue. On completion, the event moves to
        `DELIVERED`

        (2XX response) or `FAILED` (non-2XX response or timeout).


        **Manual retries replace the automatic retry loop.** If the target event

        is still `PENDING`, retrying it removes it from the normal automatic
        retry

        flow — the manual retry becomes the only remaining attempt. See

        [Delivery event
        lifecycle](/resources/alert-webhooks#delivery-event-lifecycle)

        for the full state machine.
      operationId: retryAlertWebhookDeliveryEvent
      parameters:
        - $ref: '#/components/parameters/alertWebhookId'
        - $ref: '#/components/parameters/deliveryEventId'
      responses:
        '204':
          description: Manual retry scheduled successfully. No response body.
        '400':
          description: Bad request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '401':
          description: Unauthorized - invalid or missing authentication token
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '404':
          description: Alert webhook or delivery event not found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
components:
  parameters:
    alertWebhookId:
      name: alertWebhookId
      in: path
      required: true
      description: The unique identifier of the alert webhook.
      schema:
        type: string
    deliveryEventId:
      name: deliveryEventId
      in: path
      required: true
      description: The unique identifier of the alert webhook delivery event.
      schema:
        type: string
  schemas:
    ErrorResponse:
      type: object
      properties:
        error:
          type: string
          description: Error message describing what went wrong
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: |
        Portal API Key (Custodian API Key). Pass as a Bearer token in the
        Authorization header.

````