Skip to main content
GET
Get Webhook Log Detail
The same fields as a log list entry, plus request and response. That makes this the only way to see what your endpoint actually replied with on a failed delivery, rather than just its status code. Take the log_id from List Webhook Logs. Each response_code, including 518 and 520, is explained on Monitor deliveries.

Authorizations

Authorization
string
header
default:<BINDBEE_API_KEY>
required

Your Bindbee API key, sent as Authorization: Bearer <BINDBEE_API_KEY>. Required on every request.

Path Parameters

log_id
string<uuid>
required

Response

Successful Response

id
string<uuid>
required

Unique identifier of the delivery attempt.

connector_id
string<uuid>
required

Connector this delivery was triggered for.

url
string
required

URL the webhook was delivered to.

method
enum<string> | null

HTTP method used to deliver the webhook.

Available options:
GET,
POST,
PUT,
DELETE
response_code
integer | null

HTTP status code returned by the receiving endpoint.

created_at
string<date-time> | null
integration_name
string | null

Integration of the connector that triggered this delivery.

end_user_name
string | null

End user of the connector that triggered this delivery.

origin_id
string | null

Origin ID of the end user associated with the connector.

webhook_action
string | null

Event that triggered this delivery.

webhook_name
string | null

Name of the webhook.

request
Request · object[]

Request sent to the webhook url.

response
Response · object[]

Response received from the webhook url.