Available Events
| Event | Description |
|---|---|
partner.created | New partner signs up or is created manually |
partner.updated | Existing partner is updated |
partner.deleted | Partner is deleted |
partner.approved | Partner is approved |
partner.rejected | Partner is rejected |
partner.archived | Partner is archived |
customer.created | New customer is created |
customer.updated | Existing customer is updated |
customer.deleted | Customer is deleted |
transaction.created | New transaction occurs |
transaction.deleted | Transaction is deleted (refund) |
Webhook Payload
When an event occurs, Partnero sends aPOST request to your configured URL with event data:
Verifying Webhooks
Each request includes a signature in theSignature header — an HMAC-SHA256 hash
of the raw request body, keyed with your webhook’s signing secret (the signature
value from your webhook configuration). Compute the same hash and compare with a
constant-time comparison.
Best Practices
Return 2xx quickly
Return 2xx quickly
Respond with a 2xx status code within 5 seconds. Process data asynchronously if needed.
Handle retries
Handle retries
Partnero retries failed webhooks. Implement idempotency to handle duplicate deliveries.
Use HTTPS
Use HTTPS
Always use HTTPS endpoints in production for security.
Common Use Cases
| Event | Use Case |
|---|---|
partner.created | Send welcome email, create account in your system |
partner.approved | Notify partner, enable portal access |
customer.created | Sync to CRM, trigger onboarding |
transaction.created | Update dashboards, notify sales team |
transaction.deleted | Handle refunds, reverse commissions |
Next Steps
Create Webhook
Subscribe to events via API
List Webhooks
View existing webhook subscriptions
