> For the complete documentation index, see [llms.txt](https://integrations.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://integrations.impact.com/partner-api-reference/partner-v15/reference/webhooks/event-notifications.md).
# Event Notifications
Inbound webhook payloads that impact.com sends to a partner-configured URL when events occur.
## Receive an event notification (GET)
> impact.com sends a GET request to your configured URL with event data as query-string parameters. This delivery mode is typically used for simple pixel-style integrations.\
> \
> The query parameters present depend on the URL template you configure in your impact.com Event Notifications settings.
```json
{"openapi":"3.1.0","info":{"title":"Partner Event Notifications API","version":"15"},"tags":[{"name":"Event Notifications","description":"Inbound webhook payloads that impact.com sends to a partner-configured URL when events occur."}],"servers":[{"url":"https://your-server.example.com","description":"Replace with the URL you configured in your impact.com Event Notifications settings. impact.com will send requests to this URL."}],"paths":{"/your-configured-path":{"get":{"operationId":"receiveEventNotificationGet","tags":["Event Notifications"],"summary":"Receive an event notification (GET)","description":"impact.com sends a GET request to your configured URL with event data as query-string parameters. This delivery mode is typically used for simple pixel-style integrations.\n\nThe query parameters present depend on the URL template you configure in your impact.com Event Notifications settings.\n","parameters":[{"name":"campaign_id","in":"query","schema":{"type":"string"},"description":"Unique identifier of the brand program the event belongs to."},{"name":"action_id","in":"query","schema":{"type":"string"},"description":"Unique identifier of the tracked action."},{"name":"status","in":"query","schema":{"type":"string"},"description":"Status of the action at the time of notification (e.g., `APPROVED`, `PENDING`, `REVERSED`)."},{"name":"payout","in":"query","schema":{"type":"string"},"description":"Commission amount paid to the partner for this action, as a decimal string."}],"responses":{"200":{"description":"Your server has acknowledged the notification successfully."},"202":{"description":"Accepted — same effect as 200 from impact.com's perspective."}}}}}}
```
## Receive an event notification (POST)
> impact.com sends a POST request with a JSON body to your configured URL when an event occurs. Your server should return a \`2xx\` response to acknowledge successful receipt.\
> \
> The fields included in the payload are determined by the URL template / body template you configure in impact.com. The schema below shows the most common fields.
```json
{"openapi":"3.1.0","info":{"title":"Partner Event Notifications API","version":"15"},"tags":[{"name":"Event Notifications","description":"Inbound webhook payloads that impact.com sends to a partner-configured URL when events occur."}],"servers":[{"url":"https://your-server.example.com","description":"Replace with the URL you configured in your impact.com Event Notifications settings. impact.com will send requests to this URL."}],"paths":{"/your-configured-path":{"post":{"operationId":"receiveEventNotificationPost","tags":["Event Notifications"],"summary":"Receive an event notification (POST)","description":"impact.com sends a POST request with a JSON body to your configured URL when an event occurs. Your server should return a `2xx` response to acknowledge successful receipt.\n\nThe fields included in the payload are determined by the URL template / body template you configure in impact.com. The schema below shows the most common fields.\n","requestBody":{"description":"Event notification payload sent by impact.com.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/EventNotificationPayload"}}}},"responses":{"200":{"description":"Your server has acknowledged the notification successfully. impact.com will not retry."},"202":{"description":"Accepted — same effect as 200 from impact.com's perspective."}}}}},"components":{"schemas":{"EventNotificationPayload":{"type":"object","description":"Shape of the JSON body impact.com posts to your configured URL. Fields are populated based on the body template you set up in your Event Notifications settings — partners typically include identifiers, status, payout amount, and any product-line detail relevant to their integration.\n","properties":{"campaign_id":{"type":"string","description":"Unique identifier of the brand program the event belongs to."},"action_id":{"type":"string","description":"Unique identifier of the tracked action this notification is about."},"status":{"type":"string","description":"Current status of the action at the time of notification (e.g., `APPROVED`, `PENDING`, `REVERSED`)."},"payout":{"type":"string","description":"Commission amount paid to the partner for this action, as a decimal string."},"items":{"type":"array","description":"Per-line-item detail for the action, when the brand sends SKU-level data.","items":{"$ref":"#/components/schemas/EventNotificationItem"}}}},"EventNotificationItem":{"type":"object","description":"A single product line item attached to the action.","properties":{"sku":{"type":"string","description":"The brand's SKU for the purchased product."},"qty":{"type":"string","description":"Quantity purchased, as a decimal string."},"amt":{"type":"string","description":"Total amount for this line item, as a decimal string."}}}}}}
```
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://integrations.impact.com/partner-api-reference/partner-v15/reference/webhooks/event-notifications.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.