Webhook config
Per-order webhook routing, retry policy, and signing settings.Fields
Example
Behavior
Endpoint resolution priority
- Search-specific endpoint: If a closeout endpoint is configured for the specific search type (e.g.,
EMPLOYMENT), that endpoint is used - Fallback endpoint: If no search-specific endpoint is configured, the fallback endpoint is used
- Organization-level configuration: If no request-level webhook configuration is provided, organization-level webhook settings are used
Retry policy
- Failed webhook deliveries are retried up to the specified
retryAttemptsnumber - Retries use exponential backoff with jitter
- After all retries are exhausted, the webhook is marked as failed
Security
- All webhook payloads are signed using HMAC-SHA256 with the provided
secret - The signature is included in the
X-Webhook-Signatureheader - Verify the signature to ensure webhook authenticity
Validation rules
- URL Format: Endpoint URLs must be valid URLs. Production webhook delivery requires HTTPS; non-production may also accept
http://localhostandhttp://127.0.0.1for local testing. - Multiple Targets: Each search type can define multiple webhook targets
- Event Filters: When
eventsis omitted, the target receives onlyverification.completed(backward compatible) - Per-Target Security: Per-target
secretoverrides the globalsecret;basicAuthaddsAuthorization: Basic ...
Related schemas
- Closeout endpoints — Search type specific endpoints
- Webhook target — Single webhook target definition
- Verification request — Main verification request schema

