ngrok Edges TCP API
TCP Edges define TCP endpoints for non-HTTP protocols.
ngrok Edges TCP API is one of 24 APIs that ngrok publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
This API exposes 12 JSON Schema definitions.
Tagged areas include Edges TCP. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a JSON-LD context, a GitHub repository, and 12 JSON Schemas.
This API exposes 5 operations across 2 paths, and defines 2 schemas. It is described by OpenAPI 3.1.0, at version 2.0.0.
Requests are made against a single base URL, https://api.ngrok.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
ngrok Edges TCP API declares
2 security schemes
for authenticating requests.
It accepts HTTP bearer tokens (bearerAuth).
An API key is passed in the header as Authorization (apiKeyAuth).
By default, every request must be authenticated.
bearerAuth— Use an ngrok API key as a Bearer token. Create API keys from the ngrok dashboard or via the API Keys endpoints.apiKeyAuth— Pass the API key in the Authorization header prefixed with 'Bearer '.
Paths & Operations 5
Across 2 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 1 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.
TCP Edges define TCP endpoints for non-HTTP protocols.
Schemas 2
The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are TcpEdge (8 properties), TcpEdgeList (3 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from ngrok 12
Other APIs ngrok publishes across the network.