Request
Headers
| Header | Required | Description |
|---|---|---|
Authorization | Yes | Bearer token with your API key: Bearer YOUR_API_KEY |
Body Parameters
This endpoint requires no body parameters. It will automatically send a test webhook to the webhook URL configured in your Business Dashboard.Response
Success Response (200 OK)
Returns HTTP status code 200 with no response body when the test webhook is successfully sent to your configured webhook URL.Example Request
Example Response
Test Webhook Payload
When you call this endpoint, UIP sends a test notification to your configured webhook URL with the following structure:Content-Type: application/jsonX-UIP-Signature: <hmac_sha256_signature>- HMAC SHA-256 signature for verification
Webhook Signature Verification
All webhook requests include anX-UIP-Signature header containing an HMAC SHA-256 signature. Your webhook handler must verify this signature to ensure requests are from UIP.
Errors
See the Error Handling Guide for comprehensive error handling strategies. Possible error codes for this endpoint: Authentication Errors:auth/missing-api-key- No API key provided in Authorization headerauth/invalid-api-key- Invalid API keyauth/revoked-api-key- API key has been revokedauth/business-archived- Business account has been archived
request/webhook-missing- Webhook URL not configured in Business Dashboardrequest/webhook-unreachable- Webhook URL is not accessible or did not return 200 status coderequest/not-found- No such registered route in API service
resource/not-found- Business not found
internal/server-error- Failed to send test webhook or process requestdata/corrupt- Webhook URL is malformed (must start withhttps://)
Implementation Flow
Configure Webhook URL
Add your webhook endpoint URL in the Business Dashboard. Must use HTTPS for production.
Implement Webhook Handler
Create an endpoint that accepts POST requests and verifies HMAC signatures
Test Webhook Configuration
Call the
/webhook/test endpoint to verify your webhook is reachable and working correctlyBest Practices
Always Verify Signatures
Validate the X-UIP-Signature header on every webhook request to prevent spoofing
Use HTTPS in Production
Webhook URLs must use HTTPS. HTTP is not allowed for security reasons.
Return 200 Quickly
Process webhooks asynchronously and return 200 immediately to avoid timeouts
Test Before Production
Use this endpoint during development to verify your webhook configuration works correctly
Common Issues
Webhook unreachable error
Webhook unreachable error
Problem: Test fails with
request/webhook-unreachable errorCauses:- Webhook URL is not publicly accessible
- Firewall blocking UIP servers
- Webhook handler not returning 200 status code
- HTTPS certificate issues
- Verify webhook URL is publicly accessible
- Check firewall rules allow UIP IP addresses
- Ensure webhook returns 200 status for test events
- Use valid HTTPS certificate
Invalid signature
Invalid signature
Problem: Webhook receives requests but signature validation failsCauses:
- Using wrong webhook secret
- Calculating signature on modified body
- Character encoding issues
- Get webhook secret from Business Dashboard
- Calculate signature on raw request body (before parsing)
- Use UTF-8 encoding for all strings
Webhook URL missing
Webhook URL missing
Problem: Test fails with
request/webhook-missing errorCauses:- No webhook URL configured in Business Dashboard
- Webhook URL field is empty
- Log into Business Dashboard
- Navigate to webhook settings
- Add your webhook endpoint URL
Malformed webhook URL
Malformed webhook URL
Problem: Test fails with
data/corrupt errorCauses:- Webhook URL does not start with
https:// - Invalid URL format
- Ensure URL starts with
https:// - Use valid URL format:
https://yourdomain.com/webhook