Webhook Receiver
Configure a receiver endpoint for Attriax delivery events and keep implementation details separate from secrets.
What the receiver handles
Webhooks are useful when another system needs to react to attribution, install, analytics, or revenue events.
Event intake
Expose an HTTPS endpoint that accepts Attriax webhook deliveries and records the delivery ID for idempotency.
Signature checks
Verify the Attriax signature header before processing payloads so spoofed requests are rejected.
Handler logic
Route event types to queues, CRM updates, support tooling, or warehouse loads without blocking the request path.
Values to collect
A repository scan can suggest the handler path, but deployment details usually come from infrastructure and operations systems.
- Production HTTPS endpoint URL.
- Development or staging endpoint URL if you want to test deliveries before production.
- Event types the receiver should subscribe to.
- Retry and idempotency behavior in the downstream service.
- Where the webhook signing secret is stored and rotated.
Setup checklist
Finish configuration inside the project workspace after the receiver is deployed.
- Deploy the receiver behind HTTPS and confirm it can answer quickly with a 2xx response.
- Add signature verification and idempotency before enabling production event subscriptions.
- Open Webhooks in Attriax, add the endpoint, select event types, and store the generated secret securely.
- Send a test delivery and inspect both the receiver logs and Attriax delivery history.