Meet WireRiftA small binary. A direct connection. Your infrastructure.InstallationNative binaries for your machine. No runtime to manage.Run your own serverThe public edge belongs to you.HTTP & WebSocket tunnelsShare web apps, receive webhooks, and keep WebSockets connected.TCP tunnelsA path for the protocols beyond HTTP.Security & accessLayer access controls around what you share.Traffic inspectorSee the request. Understand the response. Try it again.Under the wireOne connection. Many independent streams.Dashboard APIYour tunnels and traffic, programmatically.ConfigurationKeep your connections together in a readable config file.Docker deploymentGive your public edge a reproducible home.Local HTTPS developmentA trusted development edge, without a public domain.TroubleshootingGet back to a working connection.
Documentation, without the detour.ESC to close
Browse documentation
DOCUMENTATION / REFERENCE

Dashboard API

Your tunnels and traffic, programmatically.

Authenticate requests

API endpoints require an Authorization: Bearer TOKEN header. The health check is public. The examples below assume the dashboard's default loopback binding.

terminal
curl -H "Authorization: Bearer YOUR_TOKEN" http://localhost:4040/api/stats

Endpoint reference

These endpoints are documented by the upstream repository. Use the source for the complete response schemas.

MethodPathPurpose
GET/healthzHealth check; no auth
GET/api/statsServer statistics
GET/api/tunnelsActive tunnels
GET/api/sessionsConnected sessions
GET/api/requestsCaptured requests
POST/api/requests/{id}/replayReplay a capture
GET / POST/api/domainsList or add domains
GET / DELETE/api/domains/{domain}Read or remove a domain
GET/api/domains/{domain}/dnsRequired DNS records
POST/api/domains/{domain}/verifyVerify domain ownership

Follow a request

Proxied requests include an X-Request-ID header. WireRift preserves an incoming ID or generates one, helping you connect application logs with captured traffic.