# GET /api/notifications/events Lists the webhooks sent to your endpoints in a time window. Newest first. This is how a receiver that was unavailable discovers what it missed: ask for the window your receiver was down for, narrow to `Failed` or `DeadLettered` if you only want the ones that did not land, and follow the continuation token until it comes back empty. The window is bounded, and a wider one is refused rather than quietly narrowed: on a recovery call, an answer silently missing eleven months would look exactly like a merchant who sent nothing. Read a longer period in steps. Each item is one delivery: an event sent to three of your endpoints is three items with the same `eventId`. Pass `eventId` to read every delivery of one event and see which of your endpoints received it. The bodies are not on this response. Fetch the ones you need individually. **Operation ID:** `notificationsGetWebhookEvents` ## Authorization Requires: Notifications.Events, merchant scope. Requires API key scope: `webhooks` Required permissions: - `Notifications.Events` ## Parameters | Name | In | Required | Type | Description | | --- | --- | --- | --- | --- | | FromUtc | query | yes | string(date-time) | Start of the window, inclusive, in UTC. | | ToUtc | query | yes | string(date-time) | End of the window, inclusive, in UTC. | | Status | query | no | [DeliveryStatus](https://devportal.demo.winkpg.io/docs/api/models/DeliveryStatus.md) | Show only deliveries in this state, or every state when omitted. | | EventType | query | no | string | Show only this exact event type, or every type when omitted. | | EventId | query | no | string | Show only the deliveries of this one event, or every event when omitted. | | MaxResultCount | query | no | integer(int32) | How many deliveries this page should carry. Defaults to `DefaultPageSize`. | | ContinuationToken | query | no | string | The token the previous page returned, or `null` for the first page. | | suppressNulls | query | no | boolean | If true, omit properties with null values. | **`Status` values** | Value | Description | | --- | --- | | `Pending` | Delivery work item created but not yet picked up by a processor. | | `Processing` | Delivery is currently being processed (in-flight). | | `Succeeded` | Delivery completed successfully. The destination acknowledged receipt. | | `Failed` | Delivery failed but may be retried. Check AttemptCount and LastError for details. | | `DeadLettered` | Delivery exhausted all retry attempts and has been moved to the dead letter queue. Requires manual investigation. | | `Skipped` | Delivery was skipped (not attempted) due to kill switch, disabled destination, or other policy reason. Check SkipReason for details. | ## Responses ### 200 One page of deliveries, plus the token that fetches the next. **Content type:** `application/json` Schema: [`WebhookEventPageDto`](https://devportal.demo.winkpg.io/docs/api/models/WebhookEventPageDto.md) Properties: - `items` (array<[WebhookEventDto](https://devportal.demo.winkpg.io/docs/api/models/WebhookEventDto.md)>): The deliveries on this page, newest first. (nullable) Fields of each item: - `id` (string(uuid)): The delivery's id, which is what the detail read takes. - `eventType` (string): The event type that was delivered, for example `transaction.created`. (nullable) - `eventId` (string): The envelope event id, which is what deduplicates a redelivery. (nullable) - `occurredAtUtc` (string(date-time)): When the originating event happened, in UTC. - `lastAttemptUtc` (string(date-time)): When the most recent attempt ran, in UTC, or `null` before the first. (nullable) - `status` ([DeliveryStatus](https://devportal.demo.winkpg.io/docs/api/models/DeliveryStatus.md)): Where the delivery got to. Values: - `Pending`: Delivery work item created but not yet picked up by a processor. - `Processing`: Delivery is currently being processed (in-flight). - `Succeeded`: Delivery completed successfully. The destination acknowledged receipt. - `Failed`: Delivery failed but may be retried. Check AttemptCount and LastError for details. - `DeadLettered`: Delivery exhausted all retry attempts and has been moved to the dead letter queue. Requires manual investigation. - `Skipped`: Delivery was skipped (not attempted) due to kill switch, disabled destination, or other policy reason. Check SkipReason for details. - `attemptCount` (integer(int32)): How many attempts have run. - `durationMs` (integer(int64)): How long the most recent attempt took, or `null` when none has run. (nullable) - `httpStatusCode` (integer(int32)): The status code the endpoint answered with, or `null` when it never answered. (nullable) - `destinationName` (string): The merchant's own name for the destination the delivery was addressed to. (nullable) - `relatedEntityType` (string): The kind of record the event was about, for example `Transaction`, or `null` when the delivery carries no such reference. (nullable) - `relatedEntityId` (string(uuid)): The id of the record `relatedEntityType` names, or `null` when the delivery carries no such reference. (nullable) - `continuationToken` (string): The token that fetches the next page, or `null` at the end. (nullable) ### 403 The credential resolves no single merchant, so there is no one merchant's deliveries to answer with. ### default The request failed. The body carries the standard error envelope: a machine-readable `error.code`, a human-readable `error.message`, and `error.validationErrors` when the failure was a validation rejection. The [error reference](https://devportal.demo.winkpg.io/docs/errors.md) lists the values `error.code` can take. **Content type:** `application/json` Schema: [`RemoteServiceErrorResponse`](https://devportal.demo.winkpg.io/docs/api/models/RemoteServiceErrorResponse.md) Properties: - `error` ([RemoteServiceErrorInfo](https://devportal.demo.winkpg.io/docs/api/models/RemoteServiceErrorInfo.md)) _Example: Business rule refused the request_ The request was understood and rejected by a platform rule. This is the shape that carries a code from the catalog above, so branch on error.code rather than on the message text. The HTTP status is the one listed against the code. ```json { "error": { "code": "Transactions:OperationNotAllowed", "message": "The operation 'Void' is not allowed on a Sale transaction with result 'Approved' and settlement state 'Settled'.", "details": "null", "data": { "correlationId": "0123456789abcdef0123456789abcdef" }, "validationErrors": "null" } } ``` _Example: Request failed validation_ One or more fields were rejected before any rule ran. error.code is null on the envelope and the causes are in validationErrors, one entry per failure. An entry carries code when the validator declared a publishable one, and memberPaths when the full path says more than members does (an element inside a collection, for example). Both keys are omitted when they would add nothing. ```json { "error": { "code": "null", "message": "Your request is not valid!", "details": "The following errors were detected during validation.", "data": { "correlationId": "0123456789abcdef0123456789abcdef" }, "validationErrors": [ { "message": "'Amount' must be greater than 0.", "members": [ "amount" ] }, { "message": "The card has expired.", "members": [ "expirationDate" ], "code": "CardData:CardExpired" }, { "message": "'Value' must not be empty.", "members": [ "value" ], "memberPaths": [ "customFields[2].value" ] } ] } } ``` _Example: Resource not found_ The id in the path names no record the caller can see. Most resources answer with a null error.code and a message naming the resource type and the id; a resource that publishes a not-found code in the catalog above carries it in error.code instead, so check for one before matching on the message. ```json { "error": { "code": "null", "message": "There is no entity Transaction with id = 7d1f3a52-0c4e-4b8a-9e21-5a6b7c8d9e00!", "details": "null", "data": { "correlationId": "0123456789abcdef0123456789abcdef" }, "validationErrors": "null" } } ``` _Example: Unexpected server fault_ Something failed that no rule anticipated. There is no code to branch on and the message is deliberately generic: the diagnostic detail stays in the platform's logs rather than going to the caller. Quote error.data.correlationId (the same value as the X-Correlation-Id response header) when you contact support: it's what finds the failure in those logs. Retrying an unsafe operation after this risks a duplicate, so reconcile before you retry. ```json { "error": { "code": "null", "message": "An internal error occurred during your request!", "details": "null", "data": { "correlationId": "0123456789abcdef0123456789abcdef" }, "validationErrors": "null" } } ``` ### 429 The request was refused because a rate limit was exceeded, or because something a later retry can clear stopped it. A rate limit refusal carries an `application/problem+json` body: wait at least the interval `Retry-After` names before retrying, then back off. Limits are tuned per deployment, so read the allowance from the response headers rather than assuming a fixed ceiling. Any other refusal carries the standard error envelope as `application/json`, and its `error.code` names the cause. **Content type:** `application/problem+json` Schema: [`RateLimitProblemDetails`](https://devportal.demo.winkpg.io/docs/api/models/RateLimitProblemDetails.md) Properties: - `type` (string) required: The problem type identifier. Always the same value: the failure is the status code itself, so there is no sub-type for a caller to branch on. (nullable) - `title` (string) required: A short, human-readable summary of the problem type. (nullable) - `status` (integer(int32)) required: The HTTP status code, repeated in the body as the problem-details format defines. - `detail` (string) required: A human-readable explanation of this occurrence of the problem. (nullable) - `retryAfterSeconds` (integer(int32)) required: How long to wait before retrying, in whole seconds, carrying the same figure as the `Retry-After` header. Always at least one: a value of zero would invite an immediate retry that is certain to be rejected again. **Content type:** `application/json` Schema: [`RemoteServiceErrorResponse`](https://devportal.demo.winkpg.io/docs/api/models/RemoteServiceErrorResponse.md) Properties: - `error` ([RemoteServiceErrorInfo](https://devportal.demo.winkpg.io/docs/api/models/RemoteServiceErrorInfo.md)) ## Example request Every block below sends the same request. Replace {{BASE_URL}} with the address of the API you are calling and {{API_KEY}} with your own key. ### cURL ```bash curl -X GET "{{BASE_URL}}/api/notifications/events?FromUtc=2026-01-01T00%3A00%3A00Z&ToUtc=2026-01-01T00%3A00%3A00Z" \ -H "api-key: {{API_KEY}}" ``` ### PowerShell ```powershell $headers = @{ 'api-key' = '{{API_KEY}}' } $response = Invoke-RestMethod -Method GET -Uri '{{BASE_URL}}/api/notifications/events?FromUtc=2026-01-01T00%3A00%3A00Z&ToUtc=2026-01-01T00%3A00%3A00Z' ` -Headers $headers ``` ### TypeScript (SDK) ```bash npm install @winkpg/winkpg-api ``` ```typescript import { Configuration, NotificationsApi } from '@winkpg/winkpg-api'; const api = new NotificationsApi(new Configuration({ basePath: '{{BASE_URL}}', apiKey: '{{API_KEY}}', })); const { data } = await api.notificationsGetWebhookEvents("2026-01-01T00:00:00Z", "2026-01-01T00:00:00Z"); ``` ### TypeScript (raw HTTP) ```typescript const response = await fetch('{{BASE_URL}}/api/notifications/events?FromUtc=2026-01-01T00%3A00%3A00Z&ToUtc=2026-01-01T00%3A00%3A00Z', { method: 'GET', headers: { "api-key": "{{API_KEY}}", }, }); const data = await response.json(); ``` ### C# (SDK) ```bash dotnet add package WinkPg.Api.Client ``` ```csharp using WinkPg.Api.Client.Api; using WinkPg.Api.Client.Client; var config = new Configuration { BasePath = "{{BASE_URL}}" }; config.AddApiKey("api-key", "{{API_KEY}}"); var api = new NotificationsApi(config); var result = await api.NotificationsGetWebhookEventsAsync(DateTime.Parse("2026-01-01T00:00:00Z"), DateTime.Parse("2026-01-01T00:00:00Z")); ``` ### C# (raw HTTP) ```csharp using var http = new HttpClient { BaseAddress = new Uri("{{BASE_URL}}") }; var request = new HttpRequestMessage(new HttpMethod("GET"), "/api/notifications/events?FromUtc=2026-01-01T00%3A00%3A00Z&ToUtc=2026-01-01T00%3A00%3A00Z"); request.Headers.Add("api-key", "{{API_KEY}}"); var response = await http.SendAsync(request); response.EnsureSuccessStatusCode(); var json = await response.Content.ReadAsStringAsync(); ``` ### Python (SDK) ```bash pip install winkpg-api ``` ```python import winkpg_api configuration = winkpg_api.Configuration(host="{{BASE_URL}}") configuration.api_key["ApiKey"] = "{{API_KEY}}" with winkpg_api.ApiClient(configuration) as client: api = winkpg_api.NotificationsApi(client) result = api.notifications_get_webhook_events("2026-01-01T00:00:00Z", "2026-01-01T00:00:00Z") ``` ### Python (raw HTTP) ```bash pip install requests ``` ```python import requests headers = { "api-key": "{{API_KEY}}", } response = requests.request( "GET", "{{BASE_URL}}/api/notifications/events?FromUtc=2026-01-01T00%3A00%3A00Z&ToUtc=2026-01-01T00%3A00%3A00Z", headers=headers, ) response.raise_for_status() data = response.json() ``` ## See also - [All documentation](https://devportal.demo.winkpg.io/llms.txt): the machine-readable index of every public page on this site.