What are Public Endpoints?

Public endpoints enable your services to receive geo-balanced internet traffic using ngrok's global points of presence. This is the most common type of endpoint and the easiest way to start.

Public endpoint URLs must:

• Use either a Domain or TCP Address
• Use the public binding

Get started

You can create a public endpoint using:

• The dashboard
• The API.

Follow the Getting Started guide to set up an ngrok account and create your first public endpoint.

Authentication

Public endpoints are useful out of the box for content you don't want to restrict access to, such as blogs or marketing sites; but they can also be used for services that require strict access control such as dashboards or private APIs.

To keep such services both public and secure, you can add a Traffic Policy to your endpoint for authentication and authorization. Traffic Policy actions enable you to do the following with your endpoints:

• JWT Validation
• OAuth
• OIDC
• IP restrictions
• Mutual TLS

Matching endpoints

A matching endpoint is a public endpoint with a hostname matching a Domain or TCP Address you've configured with ngrok.

Matching endpoints are subject to the following restrictions:

Endpoint Protocol	Required Port
http	80
https	443
tls	443
tcp	Any

API

Public endpoints can be created programatically. Consult the documentation on Endpoint APIs.

Pricing

Public endpoints are available on all plans. Consult the Endpoints Pricing documentation for billing details.