Custom Request Headers
Send custom HTTP headers with every check — bearer tokens, User-Agents, host overrides. Validated as JSON, 4 kB cap.
Custom Request Headers#
Send extra HTTP headers with every check so LemWatch can reach endpoints that need authentication, a specific User-Agent, or a host override.
Format#
A JSON object — keys are header names, values are strings.
{
"Authorization": "Bearer eyJhbGciOi...",
"User-Agent": "LemWatch-Probe/1.0",
"X-Forwarded-Host": "api.example.com"
}Rules#
"" is treated as "no custom headers"Common patterns#
Protect a staging environment
{ "Authorization": "Basic dXNlcjpwYXNz" }Allowlist past your WAF
{ "X-LemWatch-Probe": "your-shared-secret" }Pin a CDN edge
{ "Host": "origin.example.com" }Security#
Headers are stored encrypted at rest. They are visible in the audit log to admins of your organization. Rotate any token if a teammate leaves.
Troubleshooting#
Authorization)Related Articles
Advanced Monitoring Fields
The four advanced site fields — response-time threshold, HTTP method, custom headers, and expected body — explained with examples.
Custom HTTP Methods & Headers
Monitor endpoints behind authentication with custom headers.
API Endpoint Monitoring
Monitor your API endpoints for uptime, response time, and expected responses.
Whois & domain expiry check
Uses RDAP to track domain expiry, auto-renew status, and registrar lock — alerts you 90, 30, 14, and 3 days before expiry.