Postback / Webhook Tester

A temporary ingest URL for postback debugging: live request feed, click id / status / payout parsing and unfilled macro detection.

Loza CRM·Updated: October 3, 2026

Quick answer

Click "Create test URL", paste the link as the postback in your affiliate network or call it with curl — incoming requests appear on the page parsed into click id, status and payout. Data lives 24 hours.

Do not send real personal data or secrets here — the body and some headers are stored for 24h.

How to use

  1. Click "Create test URL" and complete Turnstile — you get a unique ingest address
  2. Set it as the postback URL in your network with its macros ({clickid}, {payout} etc.) or fire it with curl
  3. Every request shows up: method, parameters, body, masked IP — parsed into click id / status / payout
  4. If the network sent a literal {clickid} instead of a value, the tool flags it as an unfilled macro
  5. The hook lives 24 hours and self-destructs — or delete it early with the button

Why you need it

Debugging a postback is a classic pain: the network fires a conversion into the void and you cannot tell whether the request arrived, let alone what parameters it carried. This tool gives you a temporary ingest URL that accepts any HTTP method and always answers 200, so the network never marks your endpoint as failing.

Each incoming request is parsed automatically: the tool looks for a click id under nine common key names (subid, clickid, cid, tid and more), a conversion status and a payout parameter, and flags literal values like {clickid}, [sub1] or %SUM% as unfilled macros — the single most common reason "postbacks don't work".

The storage schema is privacy-aware: only query parameters, a body capped at 20 KB and a six-header whitelist are kept — Authorization and cookies are never stored, and the sender IP is saved masked. The event feed requires a separate view key that lives only in your session.

Loza CRM computes these metrics for your campaigns automatically — try it free.

Open Loza CRM

FAQ

How long does a test hook live?
24 hours from creation, then the URL stops accepting events. You can delete it earlier with the button. At most 50 recent requests are kept.
Why did my postback arrive without a click id?
Usually the wrong macro was used or it was not filled: if the network sent a literal {clickid}, the tool shows it in red as an unfilled macro — check your network's macro syntax.
Is it safe to send real data here?
Do not send personal data or secrets. Parameters, a 20 KB body cap and six whitelisted headers are stored — auth and cookies are not, and IPs are masked. Everything is wiped after 24 hours.
Which HTTP methods are accepted?
All of them: GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS. The endpoint always returns 200 so the network does not flag the URL as down.

Other tools