Splynx API

Splynx API Integration

Splynx API integration helps ISPAgents coexist with existing Splynx deployments while operators validate billing, access, support, and migration workflows.

Migration plan
Connector health

Integration status and evidence

paths online
3
actions queued
18
critical fails
0
RADIUSPolicy sync and CoAOK
RouterMikroTik command previewOK
CPEProtocol agent telemetryOK
Every connector action shows owner, object, result, and recovery evidence.
Page type
Integrations
Primary search
Splynx API integration
Updated
2026-05-24

API integration makes migration safer

ISPs using Splynx should be able to evaluate ISPAgents without manually duplicating every record. API integration can validate coexistence while the operator validates customer data, service identifiers, balances, payments, and access control behavior.

What to synchronize

DataWhy it matters
CustomersSupport and finance need reliable names, contacts, account state, and location.
ServicesAccess workflows depend on the right plan, service identifier, NAS, router, and policy.
Invoices and balancesFinance must reconcile old and new systems during migration.
PaymentsRestoration and collection actions need clear payment evidence.
RADIUS and router mappingControlled access workflows need accurate user, NAS, policy, queue, or address-list references.

Coexistence workflow

Start read-only, import the baseline, compare counts and balances, then run a single controlled workflow such as paid restoration. Expand only after the team can explain every difference.

FAQ

Is API integration required for every migration?

No. CSV and Excel may be enough for smaller migrations. API integration is useful when the ISP needs coexistence or repeated sync during testing.

What should not be automated first?

Avoid high-risk access changes until identifiers, policies, balances, and rollback steps are verified.

Next step

See how this works in your network.