WebhookLab
Event delivery, contracts, signatures, replay, async jobs, and evidence.
Validate WebhookLab in BrowserOps
BrowserOps checks the public page, metadata, accessibility, console state, network failures, trace propagation, and screenshot evidence without taking over WebhookLab's product role.
- Target
- https://webhooklab.platphormnews.com
- Journey
- Webhooks homepage smoke
Boundary
Public preview validates intent. Browserbase runs create real browser evidence. Downstream delivery is tracked as a handoff and is never marked accepted without a response.
Integration run state
Preview the BrowserOps plan publicly, then run a Browserbase-backed check through BrowserOps-managed service credentials.
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
no responsedegraded
trace echo not confirmed
Browserbase Runtime
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 use BrowserOps-managed service credentials or service-to-service authorization.
Handoff Examples
WebhookLab remains the event surface; BrowserOps records a managed browser request when real browser evidence is needed.