Overview
Webhooks notify you immediately when order status changes, eliminating the need to poll the API. Get instant updates when providers accept, schedule, or complete orders.Webhook functionality may be under development. Check with support for current availability and configuration options.
How Webhooks Work
- Configure your endpoint URL
- Offergrid sends POST requests when events occur
- Your server processes the event
- You respond with 200 OK
- Offergrid retries on failure
Reseller Webhook Events
order.status_changed
Triggered when order status updates:order.scheduled
Installation/activation scheduled:order.completed
Service activated:order.rejected
Provider rejected order:Setting Up Webhooks
Configuration process may vary. Contact support for current setup instructions.
Create Webhook Endpoint
Handle Events
Verifying Signatures
Always verify webhooks are from Offergrid:Best Practices
Respond immediately
Respond immediately
Return 200 OK within 5 seconds. Process events asynchronously.
Verify signatures
Verify signatures
Always check webhook signatures to prevent fake events.
Handle duplicates
Handle duplicates
You may receive the same event multiple times. Use idempotency keys.
Implement retries
Implement retries
If processing fails, queue for retry. Don’t lose events.
Log all events
Log all events
Keep webhook logs for debugging and audit trails.
Monitor webhook health
Monitor webhook health
Track delivery rates and processing times. Alert on failures.
Testing Webhooks Locally
Use ngrok
Send Test Events
Common Use Cases
Auto-Update CRM
Customer Notifications
Commission Tracking
Next Steps
API Integration
Learn about API integration
Tracking Orders
Monitor order status
API Reference
Complete API documentation
Authentication
API key management