S2S postback endpoint · Affilinext Help Center

Advertisers that can't use an API key report conversions by calling the postback URL from their server. It does the same thing as POST /api/v1/conversions, authenticated by a token in the URL instead.

GET https://app.affilinext.com/postback?click_id={click_id}&txid={order_id}&status=approved&revenue={amount}&token=YOUR_TOKEN

POST with the same fields as a form or JSON body also works. If your network uses a branded postback domain, use that instead.

Parameters

Parameter	Also accepted as	Description
`click_id`	`clickid`, `cid`	The click ID from the offer URL. Required unless `coupon` is sent.
`txid`	`transaction_id`, `conversion_id`	Your unique order or event ID
`status`		`approved` (default), `pending` or `rejected`
`revenue`	`sale_amount`	Sale amount
`payout`	`sum`	Only used if the campaign accepts advertiser-supplied payouts
`currency`		e.g. `USD`
`goal`	`event`	Event name for multi-goal campaigns
`coupon`	`coupon_code`, `promo_code`	Attribute by coupon instead of click ID
`token`		Your advertiser postback token, or the network's global token
`secret`		The campaign's postback secret — an alternative to `token`
`advertiser_id`		Optional. If sent, it must match the click's advertiser.

A parameter left as an unfilled macro — a literal {revenue} — is ignored rather than read as zero.

Responses

Code	Meaning
`201`	Conversion recorded
`200`	Already recorded: `"status": "duplicate"` (no change) or `"updated"` (new status or amount)
`400`	No click ID or coupon
`401`	Missing or wrong `token` / `secret`
`403`	`advertiser_id` doesn't match the click
`404`	Unknown click ID or coupon
`422`	The click was rejected by fraud checks

Every call is logged with its response, so you can debug it from Postback Logs in the app.

For a step-by-step setup guide, see Send conversions with an S2S postback.