API
API and connector platform
ISPAgents API direction for customer, billing, access, inventory, support, field service, payment, RADIUS, router, and CPE connector workflows.
APIs should support operations
The API should expose workflows that matter to ISPs: customer state, service state, payments, access control, tickets, jobs, inventory, and connector evidence.
- Customer and service state
- Billing and payments
- Access workflows
- Audit evidence
Custom agents need clear contracts
Custom connectors for private networks, NATed sites, vendor systems, and regional providers need stable contracts and safe execution boundaries.
- Connector health
- Scoped permissions
- Retry handling
- Change evidence