WebhookLab
Event delivery, contracts, signatures, replay, async jobs, and evidence.
Validate WebhookLab in BrowserOps
Preview the plan publicly or launch the trusted-domain browser check using the server-side Vercel PLATPHORM_API_KEY when no key is entered.
Live Public Connectivity
WebhookLab public surfaces are reachable; configure a BrowserOps receive-handoff route before claiming downstream delivery.
health
200passed
trace echo not confirmed
apiDocs
200passed
trace echo not confirmed
llms
200passed
trace echo not confirmed
mcp
200passed
trace echo not confirmed
handoffReceiver
404degraded
trace echo not confirmed
Browserbase Runtime
Protected BrowserOps runs for WebhookLab use browserbase. Browserbase is configured, project is configured, and session metadata records BrowserOps run ID, journey ID, and target service without storing target URLs in Browserbase metadata.
Capability Mapping
BrowserOps may call
- read_event_contract
- verify_public_delivery_page
BrowserOps may receive
- workflow_state_changed
- signed_browserops_request
Transport and Boundary
- Preferred transports
- asyncapi, webhook, openapi
- API docs
- https://webhooklab.platphormnews.com/api/docs
- MCP status
- not advertised
- Auth boundary
- Public event schemas are readable; replay, signing, and callback mutation require PLATPHORM_API_KEY.
Handoff Examples
WebhookLab remains the event surface; BrowserOps marks protected execution when a real browser run is requested.