AXAffilinext Help Center

Webhooks & postbacks

Monitor signed inbound webhooks, manage advertiser webhook secrets, retry publisher postbacks and generate signed test payloads. For network admins.

For advertisers who send conversions as signed JSON webhooks instead of query-string postbacks. Watch every inbound webhook, give each advertiser its own signing secret, and keep an eye on the queue of postbacks going out to publishers.

What you can do here

  • Overview — Platform endpoints and the publisher postback queue at a glance.
  • Inbound Logs — Every webhook received: source, status (processed, rejected, duplicate, failed), event, click ID, campaign, payout and whether the signature checked out.
  • Publisher Postback Logs — Outgoing postbacks by status (pending, success, failed, exhausted) with Retry All Failed.
  • Advertiser Settings — Choose an advertiser to see or regenerate its webhook secret. A new secret is shown once — copy it then.
  • Webhook Tester — Builds a signed cURL command for a sale, lead, install or click test. It doesn't send anything — run the command yourself.

Limitations

  • Depends on: Logs need PostgreSQL and the NestJS service; without them the page says “NestJS + PostgreSQL required”.
  • Depends on: Only available when your plan includes Webhooks.
  • Restricted: Regenerating a secret breaks the advertiser's integration until they update it.

Common mistakes

  • Signing a re-serialised body — Sign the exact bytes you send. Re-encoding JSON (spacing, key order) changes the signature.
  • Clock drift — Timestamps more than 5 minutes off are rejected; keep the sender's clock in sync.