Send an event to a destination again

Asks for the event behind this attempt to be delivered to the same destination again. Needs sending: write. The same action as the retry button beside that attempt in the delivery portal.

It re-delivers the event, it does not resend the attempt. What comes back is a new attempt against the same event and the same destination, numbered one higher and marked manual: true. The attempt this was called on is unchanged.

Reach for it when a delivery failed for a reason you have since fixed and the delivery service has stopped retrying on its own. It is not the way to catch up after an outage: those retries happen without being asked, and replaying an event a consumer already processed is a duplicate they have to handle.

A 202 means the delivery service has the request. The delivery happens after the response, and the attempt it produces appears in the log shortly afterwards rather than immediately.

A destination that has been switched off answers 422, since a disabled destination is skipped rather than queued. Switch it back on in the portal first.

Takes no body: which event and which destination are both properties of the attempt. It does take ?newsletter=, for the reason GET /delivery-attempts/{attempt} does. Leave it out if your credential reaches exactly one newsletter.