Overview
The Ping endpoint is a simple health check that allows you to:- Test connectivity to Modulus Labs webhook servers
- Verify API availability and response time
- Confirm your network can reach the webhook API endpoints
Test Connectivity
Verify your application can reach Modulus Labs webhook servers
Check API Availability
Confirm the Webhook API is online and responding
Endpoint
This endpoint does not require authentication. It’s a public health check endpoint that anyone can access to verify Webhook API connectivity.
Request
Headers
| Header | Value | Required |
|---|---|---|
accept | */* | No |
Parameters
This endpoint does not accept any parameters.Request Body
This endpoint does not require a request body.Response
Success Response
Status Code:200 OK
Headers:
If you receive
Pong!, the Webhook API is available and your network connectivity is working!Error Responses
500 Internal Server Error
500 Internal Server Error
Status Code:
500Cause: Unexpected server errorSolution:- Retry the request
- If the issue persists, contact Modulus Labs support
- Report the time of occurrence for troubleshooting
503 Service Unavailable
503 Service Unavailable
Use Cases
Integration Testing
Verify webhook API connectivity during development and testing
Health Monitoring
Include in your application’s health check endpoints
CI/CD Pipeline
Test API availability in automated deployment workflows
Credential Validation
Confirm secret key is valid before registering webhooks
Testing Checklist
Use this checklist to verify your Webhook API setup:Monitoring & Health Checks
Include the Ping endpoint in your monitoring strategy:Monitoring Example
Best Practices
Call Before Webhook Operations
Call Before Webhook Operations
Test connectivity before creating or updating webhooks:
Implement Timeouts
Implement Timeouts
Always set appropriate timeouts to avoid hanging:
Log Health Check Results
Log Health Check Results
Keep track of health check outcomes for debugging:
Use in Startup Checks
Use in Startup Checks
Verify Webhook API connectivity when your application starts:
Troubleshooting
Network Timeout
Network Timeout
Symptom: Request times out without responsePossible Causes:
- Firewall blocking HTTPS requests
- DNS resolution problems
- Network connectivity issues
- Check firewall rules allow HTTPS (port 443)
- Test DNS resolution:
nslookup webhooks.sbx.moduluslabs.io - Try from a different network
- Increase timeout duration
SSL Certificate Error
SSL Certificate Error
Symptom: SSL/TLS certificate validation failsPossible Causes:
- System time incorrect
- Missing CA certificates
- Corporate proxy intercepting SSL
- Verify system time is correct
- Update SSL certificates on your system
- Configure proxy settings if applicable