Integrations
Two kinds of connection.
One reads utilisation from a system you already own. The other reads invoices from carriers who mostly send files. Every named system carries its status label.
Request a pilot
Two connections, one paragraph each
- Read-only
Monitoring systems
Utilisation read from the system your network team already runs, over one read-level key, at hourly and daily resolution, with the platform's own coverage figure beside every bucket. PRTG is the first connector, and six more are surveyed and carry their status.
- Catalogue
Carriers
A catalogue of 2,231 operators across 228 countries and territories, built from open reference data, behind carrier matching. Invoices arrive as files today: CSV and XLSX mappings and PDF extraction are built, e-invoicing XML and carrier portals are planned, and the carrier API path carries a research-only label.
Every status is stated
A status label sits beside every system named on these pages, and it says where that connection stands today. Built means the code is in the product and runs today; its accuracy on one carrier's real invoices is measured in a pilot. In progress means the work is under way and tested against recorded fixtures. Planned means the platform is surveyed and the connector is scheduled, and research only means the interface is defined while the work is scoped. The label sits on the entry itself, so you read it where you read the system.
How a connection is added
The same four moves for a monitoring system and for a carrier format.
- SurveyWe read the platform's API or the carrier's invoice layout and write down the shape it exposes: interface inventory and historic series, or the header row and the line structure.
- FixtureA recorded sample, captured from a real installation or a real invoice, becomes the test the connector or the parser must pass. Units and totals are asserted, so a factor of eight or a mis-summed page fails in the test rather than in a board pack.
- LabelThe entry on the integrations page moves from planned to in progress when the work is under way against fixtures, and to built when the code runs in the product. Accuracy on one carrier's real invoices is then measured in a pilot, and the page says so.
- RunA monitoring read runs on a request budget with one request in flight per server. A carrier format runs through a saved mapping keyed to its header row, and a changed layout opens a review item rather than a wrong figure.
Questions about connections
Do you install anything inside our network?
Every read is outbound from Riopex to your monitoring system's own API, on a read-level key. The monitoring page sets out what that key can reach and how it is held.
Our carrier is missing from the list. Can you read its invoices?
Yes. The list names the carriers whose formats we build for first. The catalogue behind matching holds 2,231 operators across 228 countries and territories, and a new format is learned once, as a saved mapping or an extraction profile, and carries its status from then on.
Which monitoring system should we have?
The one you run. PRTG is first; SolarWinds, ManageEngine OpManager, Zabbix, LibreNMS, Cisco Meraki and Fortinet FortiAnalyzer are surveyed, and each carries its status on the monitoring page. A system missing from that list is a conversation, because the connector interface is designed so a new one is an addition rather than a rewrite.
Why files rather than carrier APIs?
A handful of carriers publish a billing API, and each gates it behind an account relationship that needs your permission and your credentials. Files arrive from every carrier today, so the file path comes first and the API path is defined as an addition.
