Stream postbacks
The Postback section — incoming receiver URL and outgoing postbacks for each status, with method, body, and headers.
Postbacks are server-to-server conversion exchange over HTTP. Configure them on every stream in its Postback section; there is no separate postbacks page. There are two directions: incoming (tracker → darkcore) and outgoing (darkcore → tracker).
For a step-by-step setup with a specific tracker, see Keitaro integration. This page is a field reference.
Incoming postback
The section displays a ready receiver URL to copy into your tracker:
https://edge.darkcorepwa.com/p?click_id={click_id}&status={status}&payout={payout}The endpoint accepts click_id, status, payout, and an optional transaction_id over GET or POST. For POST, form-urlencoded and JSON bodies are supported; query parameters take precedence over body values. Below the URL, the accepted statuses table shows aliases (the &status= values) for every active conversion type. See Postback parameters for the full parameter and rules reference.
There is no currency field: all payout values are treated as US dollars. Convert the amount before sending if the offer is in EUR/GBP.
Outgoing postback
Each status (install plus every active conversion type) has its own outgoing delivery. An empty URL disables the postback for that status.
| Field | Type | What it controls | Default |
|---|---|---|---|
| URL | text | Where to forward this status's conversion | empty |
| Macros button | insertion | Adds a token such as {click_id} at the cursor position | — |
| HTTP method | select | GET / POST / PUT | GET |
| Content type | select | Form / JSON / Text (POST/PUT only) | Form |
| Body template | textarea | Request body with macros (POST/PUT only) | — |
| Custom headers | key/value pairs | Arbitrary HTTP headers, such as an API key | empty |
The advanced settings (method, type, body, headers) expand beneath the URL with a button.
Content type and escaping
| Type | Content-Type | Macro escaping in the body |
|---|---|---|
| Form | application/x-www-form-urlencoded | URL-encoded |
| JSON | application/json | JSON-safe |
| Text | text/plain | no escaping |
Example routing by status:
https://kclick.example.com/postback?subid={click_id}&status=leadURL: https://kclick.example.com/postback
Body: subid={click_id}&status=sale&payout={payout}¤cy={currency}
Header: X-Api-Key: secret123Templates can use the full set of macros.
Outgoing postbacks retry up to 4 times with increasing delay; 4xx errors are final. If your tracker filters requests by User-Agent, allow darkcorepwa-postback/1.0.
Check delivery
Open Tracker logs and select Outbound S2S. Filter by date range, status, stream, or click ID.
Row details show the URL, delivery status, HTTP code, attempt count, and error text.
How statuses become conversion types
The status value from an incoming postback matches a conversion type by its key or aliases. For example, reg, registration, and lead map to registration. If deposit arrives without a prior registration, darkcore automatically creates a registration event so the funnel and pixels remain consistent.