Accessing webhook management
To manage your webhooks:1
Log in to Rise app
Navigate to your Rise dashboard at app.rise.com
2
Go to Developer section
Click on the Developer section in the main navigation
3
Open webhooks
Click on “Webhooks” in the sidebar menu
Webhook overview page
The webhooks page shows all your webhook endpoints in an organized list. Each webhook displays:Endpoint URL
The destination where events are sent
Status indicator
Active/Inactive status with visual indicators
Event count
Number of subscribed event types
Performance metrics
Last delivery time and success rate statistics
Creating a new webhook
To create a new webhook endpoint:1
Start creation
Click the “Create Webhook” button on the webhooks overview page
2
Configure basic settings
Fill out the webhook form with:
- Endpoint URL: Your server’s webhook endpoint (HTTPS recommended for production)
- Secret: A secure string for signature verification
- Team: Select company-level or specific team (optional)
3
Select event types
Choose which events you want to receive:
- Browse available events by category
- Search for specific event types
- Use “Select All” for comprehensive coverage
4
Configure delivery settings
Set optional delivery parameters:
- Active: Enable/disable the webhook immediately
- Retry policy: Customize retry attempts (uses defaults if not specified)
- Timeout: Set request timeout (uses system default if not specified)
5
Save webhook
Click “Create Webhook” to save your configuration
Make sure to save your webhook secret securely - you’ll need it for signature verification in your code.
Editing an existing webhook
To modify a webhook configuration:1
Select webhook
Click on any webhook from the list to open its details page
2
Enter edit mode
Click the “Edit Webhook” button to modify settings
3
Update configuration
Modify any fields you want to change:
- Change the endpoint URL
- Update the secret key
- Modify event subscriptions
- Update team assignment
4
Save changes
Click “Save Changes” to apply your updates
If you change the webhook secret, make sure to update your server code with the new secret before saving, or webhook deliveries will start failing.
Managing event subscriptions
You can easily modify which events a webhook receives:Adding new events
From webhook details
From webhook details
- Open webhook details and go to the “Events” tab
- Click “Add Events” button
- Select additional event types from the available list
- Save your changes
Bulk selection
Bulk selection
- Use “Select All” to subscribe to all available events
- Use category filters to add all events from specific categories
- Search functionality to quickly find specific event types
Removing events
1
Navigate to events
Go to webhook details and click the “Events” tab
2
Remove events
Click the X button next to any events you want to unsubscribe from
3
Bulk removal
Use “Clear All” to remove all event subscriptions, or select multiple events for batch removal
Webhook status management
Control when your webhooks are active or inactive:Deactivating webhooks
- Temporary deactivation
- Permanent deactivation
Useful for maintenance or debugging:
- Toggle the status to deactivate the webhook
- Perform your maintenance work on your endpoint
- Reactivate when ready by toggling status back to active
Events that occur while a webhook is deactivated are not queued - they will be lost. Reactivate your webhook as soon as maintenance is complete.
Webhook security settings
Updating webhook secrets
1
Access security settings
Go to webhook details and find the security section
2
Generate new secret
Click “Update Secret” to generate or enter a new webhook secret
3
Update your code
Before saving, update your server code with the new secret
4
Test the change
Use the test webhook feature to verify the new secret works correctly
5
Save configuration
Only save the new secret after confirming your code works with it
Viewing webhook details
The webhook details panel shows:Configuration
Webhook ID, creation date, current settings, and security configuration
Performance
Recent delivery statistics and success rates
Security
Secret management, signature verification status, and HTTPS usage
History
Recent delivery attempts, failures, and retry information
Webhook testing
Test your webhooks without waiting for real events:Quick test
Quick test
- Go to webhook details page
- Click “Test Webhook” button
- Select an event type to simulate
- Click “Send Test Event”
- Check your server logs to confirm receipt
Advanced testing
Advanced testing
- Choose specific versions if multiple event versions are available
- Test different event types to verify your handler works for all subscribed events
- Check delivery history for any errors or issues
Monitoring webhook performance
Keep track of your webhook health with built-in monitoring:Key metrics
Success rate
Percentage of deliveries that succeed on the first attempt
Response time
Average time your endpoint takes to respond to webhook requests
Retry rate
Percentage of deliveries that require retry attempts
Delivery history
Access detailed delivery logs to track performance:- Successful deliveries - Events delivered with 200 response
- Failed deliveries - Events that couldn’t be delivered
- Pending retries - Events waiting to be retried
- Response details - HTTP status codes and response times
Deleting webhooks
To permanently remove a webhook endpoint:1
Access webhook details
Open the webhook you want to delete
2
Initiate deletion
Click the “Delete Webhook” button (usually in the danger zone)
3
Confirm deletion
Type the webhook name or confirm deletion in the dialog
Warning: Deleting a webhook cannot be undone. All delivery history will be permanently lost. Consider deactivating instead if you might need the webhook again.
Team-level webhook management
For organizations using teams, Rise supports different webhook scopes:- Company-level webhooks
- Team-specific webhooks
Scope: Entire company
- Receive events for all company activities
- Managed by company administrators
- Visible to all team members (with appropriate permissions)
- Best for: Company-wide integrations, reporting, analytics
Company-level webhooks are ideal for integrations that need visibility into all organizational activity.
Best practices for webhook management
Organization strategies
Use descriptive names
Use descriptive names
Why it matters: As your integration grows, you’ll likely have multiple webhooks for different purposes.Best practices:
- Use clear descriptions like “Order confirmation emails to customers”
- Include the purpose: “Inventory sync to warehouse system”
- Add environment indicators: “Production payment processing”
Group by function
Group by function
Organize webhooks by business function:
- Customer-facing: Payment confirmations, order updates, account notifications
- Internal systems: Analytics, reporting, inventory management
- Third-party integrations: CRM sync, accounting software, marketing tools
- Development: Testing, staging, debugging webhooks
Regular maintenance
Regular maintenance
Quarterly review process:
- Remove unused webhooks from discontinued features
- Update descriptions for changed purposes
- Review and rotate webhook secrets
- Clean up test/development webhooks
- Monitor performance trends
Security practices
Secret rotation
Regularly rotate webhook secrets, especially after team member changes or security incidents
Monitor access
Track who has access to webhook management and review permissions periodically
HTTPS recommended
HTTPS recommended for production endpoints; verify SSL certificate validity when using HTTPS
Activity monitoring
Watch for unusual patterns in delivery failures or response times
Performance optimization
Subscribe selectively
Subscribe selectively
Principle: Only subscribe to events you actually needBenefits:
- Reduces server load and bandwidth usage
- Simplifies debugging and monitoring
- Lowers costs if you pay for webhook processing
- Easier to maintain and understand
Optimize response times
Optimize response times
Target: Respond within 5 seconds, ideally under 2 secondsStrategies:
- Return 200 status immediately upon receipt
- Queue heavy processing for background jobs
- Optimize database queries and external API calls
- Monitor response time trends
Handle failures gracefully
Handle failures gracefully
Design for resilience:
- Implement idempotent event processing
- Handle duplicate events safely
- Log failures for investigation
- Set up alerting for high failure rates
Troubleshooting common issues
Webhook not receiving events
1
Check webhook status
Ensure the webhook is active (not deactivated) in the Rise app
2
Verify event subscriptions
Confirm you’re subscribed to the event types you expect to receive
3
Review delivery history
Check if Rise is attempting deliveries but they’re failing
4
Test connectivity
Use the built-in test feature to send a test event immediately
High failure rates
Server connectivity issues
Server connectivity issues
- Verify your server is accessible from external networks
- Check firewall settings and port availability
- Ensure your endpoint URL is correct and responds to POST requests
- Test SSL certificate validity for HTTPS endpoints
Response time problems
Response time problems
- Optimize slow database queries or external API calls
- Move heavy processing to background queues
- Increase server resources if needed
- Monitor response times and set up alerting
Code errors
Code errors
- Check server logs for errors during webhook processing
- Verify signature verification logic is correct
- Test with different event types to isolate issues
- Use the webhook test feature to debug specific problems
What’s next?
Now that you can manage webhooks effectively:Event Types Reference
Explore all available events and their complete data structures
Testing Strategies
Learn advanced testing techniques for development and staging
Delivery Mechanics
Understand how Rise delivers webhooks and handles retries
Monitoring Guide
Deep dive into performance tracking and troubleshooting
Pro tip: Start with fewer, well-configured webhooks and gradually add more as your integration grows. It’s easier to manage and debug a smaller number of properly configured webhooks than many poorly configured ones.