#### Description:

This API method retrieves the logs of webhook notifications sent to a partner within a specified time range. It allows partners to monitor webhook delivery, inspect past payloads, and troubleshoot potential issues with event delivery or endpoint availability.

Endpoint:

GET https://api.banking.netevia.dev/api/Partners/webhooks/log

Functionality:

Purpose: To fetch a history of webhook attempts, including delivery status, timestamps, and response data.
Use Case: Useful for debugging failed webhook calls, auditing event flow, or confirming successful delivery of notifications.

Request Headers:

Authorization: Bearer token required for authenticating the partner.
Content-Type: application/json

Query Parameters:

Parameter	Type	Required	Description
`startDate`	date-time	No	Start of the date range for filtering logs (ISO 8601 format).
`endDate`	date-time	No	End of the date range for filtering logs (ISO 8601 format).
`skip`	int32	No	Number of records to skip for pagination. Defaults to `0`.
`take`	int32	No	Number of records to return. Defaults to `100`. Maximum limits may apply.

Example Request:

GET /api/Partners/webhooks/log?startDate=2025-04-01T00:00:00Z&endDate=2025-04-10T23:59:59Z&skip=0&take=50
Host: api.banking.netevia.dev
Authorization: Bearer {partnerToken}
Content-Type: application/json

Response Codes:

200 OK: Successfully retrieved the logs.
400 Bad Request: Invalid query parameters or date formats.
401 Unauthorized: Authentication token is invalid or missing.
500 Internal Server Error: Unexpected error occurred while retrieving logs.

Notes:

Pagination: Use skip and take to navigate large result sets efficiently.
Date Range: If startDate and endDate are not provided, the API may default to a recent range or return all available logs.
Monitoring: This endpoint is essential for operational visibility into webhook activity and system-to-system integrations.