You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: agent/api.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,7 +48,7 @@ The ngrok agent API guarantees that breaking changes to the API will never be ma
48
48
49
49
<Note>
50
50
51
-
The ngrok agent API accessible at `http://localhost:4040/api` supports only the v2 agent configuration format. If you are using or planning to use configuration version 3, refer to the [Agent Config Version 3](https://ngrok.com/docs/agent/config/v3/) documentation for guidance.
51
+
The ngrok agent API accessible at `http://localhost:4040/api` supports only the v2 agent configuration format. If you are using or planning to use configuration version 3, refer to the [Agent Config Version 3](/agent/config/v3/) documentation for guidance.
Copy file name to clipboardExpand all lines: agent/changelog.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ sidebarTitle: Changelog
7
7
8
8
### ngrok agent 3.30.0 \[2025-09-23\]
9
9
10
-
- A new agent HTTP API, `/api/endpoints`, has been introduced that corresponds to the [agent config version 3 format](https://ngrok.com/docs/agent/config/v3/)
10
+
- A new agent HTTP API, `/api/endpoints`, has been introduced that corresponds to the [agent config version 3 format](/agent/config/v3/)
11
11
- Endpoints and tunnels deleted via the agent API will be properly reflected in the Dashboard
| `--certificate-pem` | chain of PEM-encoded certificates, leaf first. See Certificate Bundles (https://ngrok.com/docs/cloud-edge/endpoints#certificate-chains). |
8040
+
| `--certificate-pem` | chain of PEM-encoded certificates, leaf first. See Certificate Bundles (https://ngrok.com/docs/universal-gateway/http#certificate-chains). |
8041
8041
| `--description` | human-readable description of this TLS certificate. optional, max 255 bytes. |
8042
8042
| `--metadata` | arbitrary user-defined machine-readable data of this TLS certificate. optional, max 4096 bytes. |
8043
-
| `--private-key-pem` | private key for the TLS certificate, PEM-encoded. See Private Keys (https://ngrok.com/docs/cloud-edge/endpoints#private-keys). |
8043
+
| `--private-key-pem` | private key for the TLS certificate, PEM-encoded. See Private Keys (https://ngrok.com/docs/universal-gateway/http#private-keys). |
8044
8044
| `--api-key` | API key to use |
8045
8045
| `--config` | path to config files; they are merged if multiple |
8046
8046
| `--log` | path to log file, 'stdout', 'stderr' or 'false' |
|`description`| string | human-readable description of this TLS certificate. optional, max 255 bytes. |
34
34
|`metadata`| string | arbitrary user-defined machine-readable data of this TLS certificate. optional, max 4096 bytes. |
35
-
|`certificate_pem`| string | chain of PEM-encoded certificates, leaf first. See [Certificate Bundles](https://ngrok.com/docs/cloud-edge/endpoints#certificate-chains). |
36
-
|`private_key_pem`| string | private key for the TLS certificate, PEM-encoded. See [Private Keys](https://ngrok.com/docs/cloud-edge/endpoints#private-keys). |
35
+
|`certificate_pem`| string | chain of PEM-encoded certificates, leaf first. See [Certificate Bundles](/universal-gateway/http#certificate-chains). |
36
+
|`private_key_pem`| string | private key for the TLS certificate, PEM-encoded. See [Private Keys](/universal-gateway/http#private-keys). |
37
37
38
38
### Response
39
39
@@ -50,7 +50,7 @@ Returns a 201 response on success
50
50
|`created_at`| string | timestamp when the TLS certificate was created, RFC 3339 format |
51
51
|`description`| string | human-readable description of this TLS certificate. optional, max 255 bytes. |
52
52
|`metadata`| string | arbitrary user-defined machine-readable data of this TLS certificate. optional, max 4096 bytes. |
53
-
|`certificate_pem`| string | chain of PEM-encoded certificates, leaf first. See [Certificate Bundles](https://ngrok.com/docs/cloud-edge/endpoints#certificate-chains). |
53
+
|`certificate_pem`| string | chain of PEM-encoded certificates, leaf first. See [Certificate Bundles](/universal-gateway/http#certificate-chains). |
54
54
|`subject_common_name`| string | subject common name from the leaf of this TLS certificate |
55
55
|`subject_alternative_names`|[TLSCertificateSANs](#tlscertificatesans-fields)| subject alternative names (SANs) from the leaf of this TLS certificate |
56
56
|`issued_at`| string | timestamp (in RFC 3339 format) when this TLS certificate was issued automatically, or null if this certificate was user-uploaded |
@@ -113,7 +113,7 @@ Returns a 200 response on success
113
113
|`created_at`| string | timestamp when the TLS certificate was created, RFC 3339 format |
114
114
|`description`| string | human-readable description of this TLS certificate. optional, max 255 bytes. |
115
115
|`metadata`| string | arbitrary user-defined machine-readable data of this TLS certificate. optional, max 4096 bytes. |
116
-
|`certificate_pem`| string | chain of PEM-encoded certificates, leaf first. See [Certificate Bundles](https://ngrok.com/docs/cloud-edge/endpoints#certificate-chains). |
116
+
|`certificate_pem`| string | chain of PEM-encoded certificates, leaf first. See [Certificate Bundles](/universal-gateway/http#certificate-chains). |
117
117
|`subject_common_name`| string | subject common name from the leaf of this TLS certificate |
118
118
|`subject_alternative_names`|[TLSCertificateSANs](#tlscertificatesans-fields)| subject alternative names (SANs) from the leaf of this TLS certificate |
119
119
|`issued_at`| string | timestamp (in RFC 3339 format) when this TLS certificate was issued automatically, or null if this certificate was user-uploaded |
@@ -170,7 +170,7 @@ Returns a 200 response on success
170
170
|`created_at`| string | timestamp when the TLS certificate was created, RFC 3339 format |
171
171
|`description`| string | human-readable description of this TLS certificate. optional, max 255 bytes. |
172
172
|`metadata`| string | arbitrary user-defined machine-readable data of this TLS certificate. optional, max 4096 bytes. |
173
-
|`certificate_pem`| string | chain of PEM-encoded certificates, leaf first. See [Certificate Bundles](https://ngrok.com/docs/cloud-edge/endpoints#certificate-chains). |
173
+
|`certificate_pem`| string | chain of PEM-encoded certificates, leaf first. See [Certificate Bundles](/universal-gateway/http#certificate-chains). |
174
174
|`subject_common_name`| string | subject common name from the leaf of this TLS certificate |
175
175
|`subject_alternative_names`|[TLSCertificateSANs](#tlscertificatesans-fields)| subject alternative names (SANs) from the leaf of this TLS certificate |
176
176
|`issued_at`| string | timestamp (in RFC 3339 format) when this TLS certificate was issued automatically, or null if this certificate was user-uploaded |
@@ -227,7 +227,7 @@ Returns a 200 response on success
227
227
|`created_at`| string | timestamp when the TLS certificate was created, RFC 3339 format |
228
228
|`description`| string | human-readable description of this TLS certificate. optional, max 255 bytes. |
229
229
|`metadata`| string | arbitrary user-defined machine-readable data of this TLS certificate. optional, max 4096 bytes. |
230
-
|`certificate_pem`| string | chain of PEM-encoded certificates, leaf first. See [Certificate Bundles](https://ngrok.com/docs/cloud-edge/endpoints#certificate-chains). |
230
+
|`certificate_pem`| string | chain of PEM-encoded certificates, leaf first. See [Certificate Bundles](/universal-gateway/http#certificate-chains). |
231
231
|`subject_common_name`| string | subject common name from the leaf of this TLS certificate |
232
232
|`subject_alternative_names`|[TLSCertificateSANs](#tlscertificatesans-fields)| subject alternative names (SANs) from the leaf of this TLS certificate |
233
233
|`issued_at`| string | timestamp (in RFC 3339 format) when this TLS certificate was issued automatically, or null if this certificate was user-uploaded |
|`public_url`| string | URL of the ephemeral tunnel's public endpoint |
43
43
|`started_at`| string | timestamp when the tunnel was initiated in RFC 3339 format |
44
-
|`metadata`| string | user-supplied metadata for the tunnel defined in the ngrok configuration file. See the tunnel [metadata configuration option](https://ngrok.com/docs/secure-tunnels/ngrok-agent/reference/config#common-tunnel-configuration-properties) In API version 0, this value was instead pulled from the top-level [metadata configuration option](https://ngrok.com/docs/secure-tunnels/ngrok-agent/reference/config#metadata). |
44
+
|`metadata`| string | user-supplied metadata for the tunnel defined in the ngrok configuration file. See the tunnel [metadata configuration option](/agent/config#common-tunnel-configuration-properties) In API version 0, this value was instead pulled from the top-level [metadata configuration option](/agent/config#metadata). |
45
45
|`proto`| string | tunnel protocol for ephemeral tunnels. one of `http`, `https`, `tcp` or `tls`|
46
46
|`region`| string | identifier of tune region where the tunnel is running |
47
47
|`tunnel_session`|[Ref](#ref-fields)| reference object pointing to the tunnel session on which this tunnel was started |
@@ -80,7 +80,7 @@ Returns a 200 response on success
|`public_url`| string | URL of the ephemeral tunnel's public endpoint |
82
82
|`started_at`| string | timestamp when the tunnel was initiated in RFC 3339 format |
83
-
|`metadata`| string | user-supplied metadata for the tunnel defined in the ngrok configuration file. See the tunnel [metadata configuration option](https://ngrok.com/docs/secure-tunnels/ngrok-agent/reference/config#common-tunnel-configuration-properties) In API version 0, this value was instead pulled from the top-level [metadata configuration option](https://ngrok.com/docs/secure-tunnels/ngrok-agent/reference/config#metadata). |
83
+
|`metadata`| string | user-supplied metadata for the tunnel defined in the ngrok configuration file. See the tunnel [metadata configuration option](/agent/config#common-tunnel-configuration-properties) In API version 0, this value was instead pulled from the top-level [metadata configuration option](/agent/config#metadata). |
84
84
|`proto`| string | tunnel protocol for ephemeral tunnels. one of `http`, `https`, `tcp` or `tls`|
85
85
|`region`| string | identifier of tune region where the tunnel is running |
86
86
|`tunnel_session`|[Ref](#ref-fields)| reference object pointing to the tunnel session on which this tunnel was started |
Copy file name to clipboardExpand all lines: getting-started/cloud-endpoints-quickstart.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -351,6 +351,6 @@ You configured a basic traffic policy to forward requests from one endpoint to a
351
351
What else can you do with these features?
352
352
353
353
- See [the cloud endpoints overview](/universal-gateway/cloud-endpoints/#use-cases) to learn more about use cases, how they compare to agent endpoints, and more.
354
-
- If you need to interact with cloud endpoints programmatically, check out ngrok's [API client libraries](https://ngrok.com/docs/api/#client-libraries).
354
+
- If you need to interact with cloud endpoints programmatically, check out ngrok's [API client libraries](/api/#client-libraries).
355
355
- See [Load Balancing with Cloud Endpoints](/universal-gateway/cloud-endpoints/forwarding-and-load-balancing/) to learn how to distribute traffic across multiple internal endpoints.
356
356
- This quickstart barely scratches the surface of what's possible with a traffic policy—check out the [Actions overview](/traffic-policy/actions/) to see what else you can do.
0 commit comments