WebhooksLogDto

One delivery attempt of a webhook: what was sent where, and what came back.

Name	Type	Description	Notes
id	Integer (int32)	The identifier of this attempt, which is what the eventId filter of GET api/2.0/settings/webhooks/log picks one record by and what PUT api/2.0/settings/webhook/{id}/retry re-sends. A retry produces a new record with a new identifier and leaves this one as it is.	[required] [example: 1]
configName	String	The name of the subscription the attempt belongs to. It is the name as it stands now, so it follows a later rename of the subscription rather than recording what it was called at the time.	[optional] [example: Room activity] [nullable]
trigger	WebhookTrigger	The event that caused the attempt, as a single bit rather than a mask - a delivery is always for one event, even though a subscription covers several.	[optional] [enum: 0, 1, 2, 4, 8, 16, 32, 64, 128, 256, 512, 1024, 2048, 4096, 8192, 16384, 32768, 65536, 131072, 262144, 524288, 1048576, 2097152, 4194304, 8388608, 16777216, 33554432, 67108864, 134217728, 268435456, 536870912, 1073741824]
creationTime	Date (date-time)	When the attempt was queued, as a UTC instant - unlike the dates of the subscription itself, which come in the portal time zone. Records come back newest first by this moment.	[optional] [example: 2024-01-15T10:30:00Z]
method	String	The HTTP method the delivery was sent with, which is POST for every webhook the portal sends.	[optional] [example: POST] [nullable]
route	String	The address the delivery was sent to, which is the subscription's URL as it stood at the time - so an older record can name an address the subscription no longer uses.	[optional] [example: https://example.com/hooks/docspace] [nullable]
requestHeaders	String	The headers the portal sent, serialised as one string, including the signature header a receiver verifies the payload with.	[optional] [example: {"x-docspace-signature":"9f86d081884c7d65"}] [nullable]
requestPayload	String	The body the portal sent, which is the event payload as JSON text. It is stored as it was sent, so it still describes the entity as it looked at the time of the event.	[optional] [example: {"id":42,"title":"report.docx"}] [nullable]
responseHeaders	String	The headers the target answered with, serialised the same way as requestHeaders. It is empty while the attempt is still on its way and on an attempt that never reached the target.	[optional] [example: {"content-type":"application/json"}] [nullable]
responsePayload	String	The body the target answered with, truncated for storage. Empty under the same conditions as responseHeaders, and also for a target that answers with no body at all.	[optional] [example: {"ok":true}] [nullable]
status	Integer (int32)	The HTTP status code the target answered. It is 0 while the attempt is still on its way and on one that never reached the target, so 0 is not a failure code - it is the absence of an answer.	[optional] [example: 200]
delivery	Date (date-time)	When the answer came back, as a UTC instant like creationTime. It is empty while the attempt is still on its way, which together with status is how a pending record is told from a finished one.	[optional] [example: 2024-01-15T10:30:00Z] [nullable]