---
title: "Redeliver the endpoint's most recent delivery"
description: "The one-click \"is it working again?\" after fixing a receiver — the per-delivery route below needs a delivery id, which means finding one first."
canonical_url: "https://twominutebilling.com/help/developers/api-reference/webhooks/redeliver-the-endpoint-s-most-recent-delivery"
---
# Redeliver the endpoint's most recent delivery

> The one-click "is it working again?" after fixing a receiver — the per-delivery route below needs a delivery id, which means finding one first.

<api-operation method="POST" path="/v1/webhook_endpoints/{id}/redeliver_latest">
<template v-slot:docs="">

SYNCHRONOUS: it calls your endpoint inline and answers with the outcome plus the request/response transcript of that call, so the reply tells you whether your receiver works now. Goes through the same delivery code the billing clock uses, and the same double-delivery guard. An open circuit breaker does NOT block it.

## Path parameters

<table>
<thead>
  <tr>
    <th>
      Parameter
    </th>
    
    <th>
      Type
    </th>
    
    <th>
      Required
    </th>
    
    <th>
      Description
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      <code>
        id
      </code>
    </td>
    
    <td>
      <code>
        string
      </code>
    </td>
    
    <td>
      <strong>
        yes
      </strong>
    </td>
    
    <td>
      The webhook endpoint's id.
    </td>
  </tr>
</tbody>
</table>

## Headers

<table>
<thead>
  <tr>
    <th>
      Parameter
    </th>
    
    <th>
      Type
    </th>
    
    <th>
      Required
    </th>
    
    <th>
      Description
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      <code>
        Idempotency-Key
      </code>
    </td>
    
    <td>
      <code>
        string
      </code>
    </td>
    
    <td>
      no
    </td>
    
    <td>
      Safely retry writes — repeats return the original response. If a write FAILED after it had already taken effect, that failure is what repeats: the key is spent, and a new attempt needs a new key.
    </td>
  </tr>
</tbody>
</table>

## Response

<table>
<thead>
  <tr>
    <th>
      Field
    </th>
    
    <th>
      Type
    </th>
    
    <th>
      Description
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      <code>
        object
      </code>
    </td>
    
    <td>
      <code>
        string
      </code>
    </td>
    
    <td>
      The object type.
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        id
      </code>
    </td>
    
    <td>
      <code>
        string
      </code>
    </td>
    
    <td>
      The delivery's id.
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        status
      </code>
    </td>
    
    <td>
      <code>
        string
      </code>
    </td>
    
    <td>
      The delivery's status.
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        attempts
      </code>
    </td>
    
    <td>
      <code>
        integer
      </code>
    </td>
    
    <td>
      Number of delivery attempts so far.
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        next_attempt_at
      </code>
    </td>
    
    <td>
      <code>
        string
      </code>
    </td>
    
    <td>
      When the next attempt is due (ISO-8601 UTC), or null.
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        last_response_status
      </code>
    </td>
    
    <td>
      <code>
        integer
      </code>
    </td>
    
    <td>
      The HTTP status your endpoint last returned.
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        attempt
      </code>
    </td>
    
    <td>
      <code>
        object
      </code>
    </td>
    
    <td>
      The ONE attempt this call just made. Live only — tmbilling stores none of it, so this response is the only place it exists; there is no endpoint to fetch it back from later.
    </td>
  </tr>
</tbody>
</table>

## Status codes

<table>
<thead>
  <tr>
    <th>
      Status
    </th>
    
    <th>
      Meaning
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      <code>
        200
      </code>
    </td>
    
    <td>
      The settled delivery plus the attempt just made
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        404
      </code>
    </td>
    
    <td>
      No such endpoint, or it is in the other partition
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        409
      </code>
    </td>
    
    <td>
      The endpoint has no deliveries yet, or one is already pending
    </td>
  </tr>
</tbody>
</table>
</template>

<template v-slot:request="">

```bash [Request]
curl -X POST "$TMBILLING_URL/v1/webhook_endpoints/whe_XXXXXXXXXXXX01/redeliver_latest" \
  -H "Authorization: Bearer $TMBILLING_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)"
```

</template>

<template v-slot:response="">
<code-group>

```json [200 OK]
{
  "object": "redeliver_latest",
  "id": "3f6c1b9e-8a2d-4c5e-9f10-2b7d4e6a8c01",
  "status": "active",
  "attempts": 0,
  "next_attempt_at": "2026-03-14T09:30:00Z",
  "last_response_status": 1,
  "attempt": {
    "outcome": "delivered",
    "latency_ms": 1,
    "error": null,
    "request": {
      "method": "POST",
      "url": "https://example.com/webhooks/billing",
      "headers": {},
      "body": "Requested by the customer."
    },
    "response": {
      "status": 1,
      "headers": {},
      "body": "Requested by the customer."
    }
  }
}
```

```json [404 Not Found]
{
  "error": {
    "type": "invalid_request_error",
    "message": "No such endpoint, or it is in the other partition"
  }
}
```

```json [409 Conflict]
{
  "error": {
    "type": "conflict_error",
    "message": "The endpoint has no deliveries yet, or one is already pending"
  }
}
```

</code-group>
</template>
</api-operation>


## Sitemap

See the full [sitemap](https://twominutebilling.com/sitemap.md) for all pages.