Public Endpoints
Specific network details for all ingress and egress connections with Perspio.
Endpoint Overview
Perspio Endpoints
Inbound Endpoints
Perspio has several dedicated inbound endpoints that provide public connectivity to the data and operational interfaces.
| Endpoint | Protocol | Description |
|---|---|---|
| ingress.perspio.io | HTTPS, MQTT, AMQP | This endpoint accepts messages from the configured connectors within the PerspioIngress interface. This is dedicated to secure messaging. |
| tcp.perspio.io | TCP | This endpoint accepts messages from the configured connectors within the PerspioIngress data interface. This is dedicated to TCP messaging. |
| webhooks.perspio.io | HTTP, HTTPS | This endpoint accepts messages from configured 3rd party systems. It is configured through connectors within the PerspioData interface |
| data.perspio.io | HTTPS | This endpoint is dedicated to communication with PerspioAgent. |
| perspio.io | HTTPS | This endpoint is dedicated to providing access to PerspioWeb. |
| share.perspio.io | HTTPS | This endpoint provides access to a DMZ component of PerspioWeb for viewing shared assets and dashboards to non-platform users. |
Outbound Endpoints
Any outbound connection attempted by Perspio will egress through the current register of Azure Public IP Ranges.
Azure IP Ranges and Service Tags
A regularly maintained list of these addresses can be accessed at the official Microsoft resource here. It is provided in JSON format.
Updated almost 2 years ago
What’s Next
Continue to check out other platform overview pages