Firewall & Security Allowlisting
If your backend server sits behind a firewall (Cloudflare WAF, AWS Security Group, iptables, or ModSecurity), ensure your webhook endpoint allows incoming automated HTTP delivery from Perkox.
Cryptographic HMAC Verification (Recommended)
&signature= parameter guarantees webhook authenticity and tamper-proofing with zero firewall maintenance. See the Postback Security & HMAC Guide.Official Egress IP Allowlist (Cloudflare Anycast)
All outbound Perkox conversion callbacks originate from these global edge CIDR blocks.
{signature} verification.Tier 1 (Firewall Allowlisting): Restricting traffic to Cloudflare Anycast CIDRs prevents unauthorized internet bots and malicious port scanners from ever probing your webhook URL.
Tier 2 (Cryptographic Authentication): Because Cloudflare edge IPs are shared across their global CDN network, validating the {signature} macro proves that the callback was specifically dispatched from your verified Perkox publisher account.
Expected Response Codes
Acknowledges successful processing. Perkox marks the postback as delivered and halts further retries.
Treated as delivery failure. Perkox queues the postback for automated exponential retry.
Retry Policy & Backoff
If your server is down or returns an error, Perkox automatically retries delivery up to 10 times over a 24-hour window using exponential backoff:
- Attempt 1: Immediately upon completion
- Attempt 2: 1 minute later
- Attempt 3: 5 minutes later
- Attempt 4: 15 minutes later
- Attempt 5: 1 hour later
- Attempts 6-10: Every 4 hours up to 24 hours total
Debugging with cURL
You can simulate an incoming Perkox postback to your local or staging server using cURL:
curl -i -X GET 'https://api.yourdomain.com/postback?player_id=test_user&reward_amount=100&payout=1.00&click_id=test_clk_001&status=approved&signature=YOUR_CALCULATED_HASH'
