Event Notifications

Inbound webhook payloads that impact.com sends to a partner-configured URL when events occur.

Receive an event notification (GET)

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.

Query parameters

campaign_idstringOptional

Unique identifier of the brand program the event belongs to.

Example: 10306

action_idstringOptional

Unique identifier of the tracked action.

Example: 1234567890

statusstringOptional

Status of the action at the time of notification (e.g., APPROVED, PENDING, REVERSED).

Example: APPROVED

payoutstringOptional

Commission amount paid to the partner for this action, as a decimal string.

Example: 5.00

Responses

200

Your server has acknowledged the notification successfully.

No content

202

Accepted — same effect as 200 from impact.com's perspective.

get/your-configured-path

GET /your-configured-path HTTP/1.1
Host: your-server.example.com
Accept: */*

No content

Receive an event notification (POST)

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.

Body

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.

campaign_idstringOptional

Unique identifier of the brand program the event belongs to.

Example: 10306

action_idstringOptional

Unique identifier of the tracked action this notification is about.

Example: 1234567890

statusstringOptional

Current status of the action at the time of notification (e.g., APPROVED, PENDING, REVERSED).

Example: APPROVED

payoutstringOptional

Commission amount paid to the partner for this action, as a decimal string.

Example: 5.00

Responses

200

Your server has acknowledged the notification successfully. impact.com will not retry.

No content

202

Accepted — same effect as 200 from impact.com's perspective.

post/your-configured-path

POST /your-configured-path HTTP/1.1
Host: your-server.example.com
Content-Type: application/json
Accept: */*
Content-Length: 138

{
  "campaign_id": "10306",
  "action_id": "1234567890",
  "status": "APPROVED",
  "payout": "5.00",
  "items": [
    {
      "sku": "APP-0016",
      "qty": "1",
      "amt": "719.10"
    }
  ]
}

No content