Skip to main content
Webhooks send real-time HTTP POST requests to your server when events occur in Partnero. Use them to sync data, trigger workflows, or update external systems automatically.

Available Events

EventDescription
partner.createdNew partner signs up or is created manually
partner.updatedExisting partner is updated
partner.deletedPartner is deleted
partner.approvedPartner is approved
partner.rejectedPartner is rejected
partner.archivedPartner is archived
customer.createdNew customer is created
customer.updatedExisting customer is updated
customer.deletedCustomer is deleted
transaction.createdNew transaction occurs
transaction.deletedTransaction is deleted (refund)

Webhook Payload

When an event occurs, Partnero sends a POST request to your configured URL with event data:
{
  "event": "partner.created",
  "data": {
    "id": "partner_123",
    "email": "[email protected]",
    "name": "John",
    "surname": "Doe",
    "created_at": "2025-05-07T10:30:00.000000Z"
  },
  "timestamp": "2025-05-07T10:30:00.000000Z"
}

Verifying Webhooks

Each webhook includes a signature for verification. Use the signature value from your webhook configuration to validate incoming requests.
Always verify webhook signatures in production to ensure requests originate from Partnero.

Best Practices

Respond with a 2xx status code within 5 seconds. Process data asynchronously if needed.
Partnero retries failed webhooks. Implement idempotency to handle duplicate deliveries.
Always use HTTPS endpoints in production for security.

Common Use Cases

EventUse Case
partner.createdSend welcome email, create account in your system
partner.approvedNotify partner, enable portal access
customer.createdSync to CRM, trigger onboarding
transaction.createdUpdate dashboards, notify sales team
transaction.deletedHandle refunds, reverse commissions

Next Steps