Create a tunnel
Choose a region and enter the base URL of your local HTTP service.
HTTP Tunnels
Give a local service a public HTTPS address. Adal CLI forwards requests to the application and returns its response to the caller.
Caller → Public HTTPS address → Adal CLI → Local service
Create a tunnel in the dashboard and connect it through Adal CLI.
Choose a region and enter the base URL of your local HTTP service.
Create a tunnel token and start Adal CLI with it. Wait for the tunnel to show as online.
Send a request to the public HTTPS address. Check the response and find the exchange in the dashboard.
Use a tunnel to test callbacks, share a demo or call a development API from another system.
The caller gets the HTTP status, headers and body from the application in the same exchange.
See the HTTP status and whether the transfer completed. Save request and response data independently when you need to inspect or download it.
Tunnels use the same balance as Inbound and Outbound. Bytes received in both bodies count even when saving is disabled.
Use a service intended for external requests. The public address serves requests while the tunnel is enabled and Adal CLI is connected.
Use a tunnel when the caller needs the response from your application in the same HTTP exchange. Use Inbound with a CLI channel for queued webhook delivery and automatic retries. Use Outbound to submit HTTP jobs through the API for background execution.