ngrok OpenAPI

Name: ngrok OpenAPI API
Brand: ngrok OpenAPI
Availability: InStock

✓ Official Vendor SpecCloud InfrastructureNetworkingBearer Token101 EndpointsREST

For Agents

Create secure tunnels to expose local services, manage edge configurations, and handle traffic routing with authentication and policy enforcement.

Connect the ngrok OpenAPI to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ngrok OpenAPI, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with ngrok OpenAPI API.

Create and manage secure tunnels to expose local services to the internet

Configure HTTPS and TCP edges with custom domains and certificates

Enforce IP restrictions and authentication policies on incoming traffic

Route requests through backends with failover and weighted load balancing

GET STARTED

Start building with ngrok OpenAPI API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use ngrok OpenAPI API for, with concrete tasks.

★ Webhook Development and Testing

Expose localhost servers to receive webhooks from external services during development. ngrok creates a public HTTPS URL that forwards requests to your local application, enabling real-time testing of Stripe, GitHub, or Twilio webhooks without deploying to staging. Tunnel sessions persist across restarts and support request inspection.

Create a tunnel session for localhost:3000 with a reserved domain and subscribe to webhook events for tunnel status changes

Remote Access to Local Services

Share local applications with remote teams or clients without deploying to a public server. ngrok creates secure tunnels with optional authentication and IP restrictions, making it safe to expose staging environments or preview builds. Supports both HTTP and TCP protocols.

Create an HTTPS edge with OAuth authentication and IP whitelist for team access to a local service on port 8080

Custom Domain Ingress Management

Route traffic from custom domains to local or cloud services through ngrok edges. Reserve domains, configure TLS certificates, and apply traffic policies like circuit breakers and request header modifications. Useful for multi-tenant applications or dynamic service routing without managing infrastructure.

Reserve the domain api.example.com, create an HTTPS edge with TLS termination, and configure a weighted backend to route traffic 80/20 between two tunnel endpoints

Secure IoT Device Access

Expose IoT devices or embedded systems behind NAT or firewalls without opening inbound ports. ngrok's TCP and TLS edges enable secure remote access to devices for monitoring, updates, or support. Supports SSH, MQTT, and custom TCP protocols.

Create a TCP edge on port 22 to provide SSH access to a Raspberry Pi behind NAT, with IP restriction to allow connections only from the admin network

AI Agent Integration for Tunnel Orchestration

Automate tunnel creation, edge configuration, and traffic policy enforcement through AI agents using Jentic. Agents can dynamically provision ingress for ephemeral environments, respond to webhook events, and enforce security policies based on runtime context. Jentic handles credential isolation and schema discovery.

Use Jentic to search for 'create a secure tunnel', load the ngrok tunnel creation schema, and execute a request to expose a local service on port 5000 with IP whitelisting

Key Endpoints

101 endpoints — securely expose local services to the internet through managed tunnels and edges.

METHOD

PATH

DESCRIPTION

POST

/tunnels

Create a tunnel session

GET

/tunnels

List all tunnel sessions

POST

/edges/https

Create an HTTPS edge

GET

/endpoints

List all endpoints

POST

/reserved_domains

Reserve a custom domain

POST

/ip_policies

Create an IP restriction policy

POST

/event_subscriptions

Subscribe to webhook events

POST

/tunnels

Create a tunnel session

GET

/tunnels

List all tunnel sessions

POST

/edges/https

Create an HTTPS edge

GET

/endpoints

List all endpoints

POST

/reserved_domains

Reserve a custom domain

POST

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

ngrok API keys are stored encrypted in the Jentic vault. Agents receive scoped access tokens — raw API keys never enter the agent's context.

Intent-based discovery

Agents search by intent (e.g., 'expose a local server') and Jentic returns matching ngrok operations with their input schemas, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct ngrok integration: 1-2 days for authentication, tunnel setup, and edge configuration. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Cloudflare API

Cloudflare offers CDN and edge networking features including Tunnels (formerly Argo Tunnel) for secure ingress

Choose Cloudflare if you need a full CDN stack with DDoS protection and global edge presence. Use ngrok for simpler tunnel-focused workflows and local development ingress.

Alternative

Akamai API

Akamai provides enterprise CDN and edge compute with similar traffic management capabilities

Choose Akamai for enterprise-scale CDN and edge compute with compliance requirements. Use ngrok for developer-first tunneling and lightweight ingress.

FAQs

Specific to using ngrok OpenAPI API through Jentic.

What authentication does the ngrok API use?

The ngrok API uses Bearer token authentication. You include your API key in the Authorization header as 'Bearer YOUR_API_KEY'. Jentic stores ngrok API keys encrypted in the credential vault and provides scoped access tokens to agents, so raw keys never appear in agent context. Get started at https://app.jentic.com/sign-up.

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. Start at https://app.jentic.com/sign-up.