ngrok OpenAPI

Can I create tunnels programmatically with the ngrok API?

Yes. Use the POST /tunnels endpoint to create tunnel sessions that expose local services to the internet. You can specify the protocol (HTTP, TCP, TLS), bind address, and metadata. The API returns the public URL and tunnel ID. Through Jentic, agents search for 'create a tunnel', load the schema, and execute the request without manual API documentation lookup.

What are the rate limits for the ngrok API?

The OpenAPI spec does not specify rate limits. Consult the ngrok documentation at https://ngrok.com/docs/api for current rate limit details by plan tier. Enterprise plans typically have higher limits.

How do I configure custom domains with the ngrok API?

Use the POST /reserved_domains endpoint to reserve a domain, then create an HTTPS edge (POST /edges/https) and associate it with the reserved domain. You can configure TLS certificates, authentication modules, and traffic policies on the edge. The API supports wildcard domains for multi-tenant routing.

Can I enforce IP restrictions on ngrok endpoints through the API?

Yes. Create an IP policy (POST /ip_policies) with allowed or denied CIDR ranges, then apply it to an HTTPS edge using the IP restriction module (POST /edges/https/{id}/routes/{route_id}/ip_restriction). The policy takes effect immediately on incoming traffic.

What webhook events does the ngrok API support?

You can subscribe to events like tunnel.created, tunnel.closed, endpoint.created, and endpoint.deleted via the POST /event_subscriptions endpoint. Specify a destination URL and the event sources you want to monitor. ngrok sends webhook payloads to your endpoint in real time. Use this for alerting, logging, or triggering automation.

How do AI agents use the ngrok API through Jentic?

Agents search Jentic for intents like 'expose a local server' or 'create a secure tunnel'. Jentic returns the relevant ngrok API operations (e.g., POST /tunnels) with their input schemas. The agent calls the operation via Jentic's execution layer, which handles authentication and request formatting. Integration time drops from days to minutes. Get started with Jentic One, the self-hosted execution layer.

Can I limit what my agent is allowed to do with the ngrok API?

Yes. Because you run Jentic One yourself, your own rules decide which ngrok operations and credentials the agent may use, so you can allow just the calls it needs, such as creating tunnels with POST /tunnels and listing them with GET /tunnels. These tunnel operations carry their configuration in the request body rather than a resource id in the path, so leaving edge (POST /edges/https), reserved-domain (POST /reserved_domains), and IP-policy (POST /ip_policies) actions out of the allowed set keeps the agent from making those changes unless you add them. Your stored ngrok API key is attached at execution time and never enters the agent's prompt or context.