Destinations

One delivery, with the body it posted

The list omits payloads because they are the largest part of a delivery and are wanted one at a time, when something has gone wrong. This returns the body exactly as it went on the wire, plus payload_timestamp and payload_signature - the two values the signature is computed over - so you can reproduce the HMAC check against your own secret and see where it diverges.

response_body is what your endpoint sent back, bounded to 4 KB.

Bodies are kept for payload_retention_days (7) after the attempt and then blanked; the delivery row itself stays, so the history of what was sent and how it went is not lost with it.

get/v1/deliveries/{id}

Request

  • Base URL: https://api.ironfang.com/render
  • URL: https://api.ironfang.com/render/v1/deliveries/{id}
  • Auth: HTTP bearer

Path parameters

idstring required

Response

The delivery. Payload is absent once purged.

attemptsinteger required
created_atstring date-time required
delivered_atstring date-time
destination_idstring uuid required
errorstring
eventstring required
idstring uuid required
job_idstring uuid required
next_attempt_atstring date-time
object_keystring
payloadstring

Last posted body; omitted from lists and after purging.

payload_atstring date-time nullable
payload_retention_daysinteger
payload_signaturestring
payload_timestampstring
response_bodystring
response_statusinteger
status'pending' | 'delivering' | 'delivered' | 'failed' required

Changes

No recorded changes to this operation across all 1 revision of this API.