Skip to content

Integration Clients ​

Integration Clients provide external systems—such as a billing application—with read-only, machine-to-machine API access. They are not normal user accounts and are designed for unattended jobs.

Who can manage clients ​

Superadmin, ISP, and Admin accounts can manage Integration Clients. Staff additionally need the relevant settings permissions. A client is always scoped to one reseller branch and its downline, so it cannot read another ISP's data.

Create a client ​

Open Integration Clients and select Create client. Give the integration a descriptive name, choose its reseller scope when needed, and add the public IP addresses or CIDR ranges from which it may connect.

The client secret is displayed only when created or rotated. Copy it directly into the external system's secure secret store; do not place it in chat, spreadsheets, or source control.

Restrict source IPs ​

The IP allowlist is deny-by-default. A client with no allowed IP addresses cannot call the integration API. Add only the external system's stable egress IPs or approved CIDR ranges, then verify access with that system's connection test.

Use the client list to review scope, allowed IPs, enabled state, and last-used time. Disable a client immediately if the external system is retired or a credential may be exposed.

Rotate or remove credentials ​

Rotate the client secret during a planned cutover: generate the new value, update the external system, verify a successful request, then retire the old value. Delete a client only when it is no longer needed.

The integration API is read-only. It can expose permitted reseller, customer, renewal, and package-assignment data, but it cannot create customers, post payments, or change service state.

Treat client secrets like passwords

A client secret plus an allowed source IP can read data within its scope. Use unique credentials per external system, restrict addresses tightly, rotate after staff/vendor changes, and disable unused clients.

Dream Radius ISP CRM