Built API-first — no screen hides behind a private interface.
Every screen in the Netxol One console uses the same APIs you get. 22 TM Forum Open APIs on live data, OpenAPI 3.1 contracts for every service, AsyncAPI 3.1 for webhook events, Standard Webhooks with HMAC-SHA256, and an OAuth 2 / OpenID Connect provider you can plug into your own apps.
- 22 TM Forum Open APIs on live data
- 2 TM Forum ODA component descriptors
- 100% on REST, OpenAPI, webhooks, AsyncAPI, OAuth 2, OpenID Connect
Customers, products, orders, bills, payments.
Writes go through the same engine as the console, so an order or payment made through the API is booked, audited and reconciled exactly like one made by staff.
TMF620 · Product Catalog
Plans, promotions and products with specifications and offerings.
TMF622 · Product Ordering
Place an order and track it through activation and fulfilment.
TMF629 · Customer
Create and update customer records; link to accounts and parties.
TMF632 · Party
Individuals and organisations with contact media and identifications.
TMF666 · Account
Billing accounts and relationships to customers and payment methods.
TMF637 · Product Inventory
What a customer actually has today across the catalog.
TMF678 · Customer Bill
Issued invoices with their lines, taxes and bill cycles.
TMF676 · Payment
Payments posted against customer bills, with status and refunds.
TMF635 · Usage
Usage records that feed rating and billing.
TMF621 · Trouble Ticket
Open and update tickets from your call-centre software.
TMF645 · Service Qualification
Serviceability check at an address or coordinate.
TMF646 · Appointment
Field appointments with slots, hold and confirm.
Services, resources, alarms, SLAs.
Both groups are described as TM Forum ODA components (CoreCommerce and Production), generated from the API code and checked against the running system.
TMF633 · Service Catalog
Technical service specifications behind the commercial offers.
TMF634 · Resource Catalog
Resource specifications: OLT ports, radio sectors, IP pools.
TMF641 · Service Ordering
Service orders decomposed from product orders.
TMF638 · Service Inventory
Active service instances per customer and resource.
TMF639 · Resource Inventory
Allocated resources: ports, VLANs, prefixes.
TMF640 · Service Activation
Request activation, suspension and configuration changes.
TMF656 · Service Problem
Service-affecting problems linked to tickets and alarms.
TMF642 · Alarm
Alarms from the network with severity and probable cause.
TMF653 · Service Test
Diagnostic tests invoked on an active service.
TMF657 · Service Quality
SLA metrics and reporting against service specifications.
Signed contracts, signed events.
OpenAPI 3.1 for the Core API (versioned /api/core/v1) and the network API, built from the routes, permissions and validation schemas; OpenAPI 3 for the ACS. AsyncAPI 3.1 describes every webhook event. Download them from Administration → Applications and generate a client in any language.
Outbound webhooks follow the Standard Webhooks specification: HMAC-SHA256 signatures with id and timestamp against replay, retries from 5 seconds to 10 hours, a delivery log with re-send, test messages and secret rotation.
OAuth 2, OpenID Connect, SAML, LDAP, SCIM.
Netxol One is an OAuth 2 authorisation server and OpenID Connect provider. Staff can sign in with your SAML or LDAP provider; SCIM 2.0 keeps users and groups in sync.
OAuth 2 · OpenID Connect
Authorization code with PKCE, client credentials, rotating refresh tokens, revocation and introspection.
SAML 2.0
Staff sign-in via your corporate identity provider.
LDAP / Active Directory
Direct bind for staff authentication.
SCIM 2.0
User and group provisioning kept in sync with your directory.
What you can build on top of Netxol One.
Which TM Forum Open APIs does Netxol One support?
22 APIs: TMF620, 621, 622, 629, 632, 633, 634, 635, 637, 638, 639, 640, 641, 642, 645, 646, 653, 656, 657, 666, 676 and 678, covering customers, products, orders, bills, payments, tickets, services, resources and alarms.
Is there an OpenAPI specification?
Yes. OpenAPI 3.1 for the Core and network APIs and OpenAPI 3 for the ACS, plus AsyncAPI 3.1 for webhook events. Signed-in administrators download them from the console.
How are webhooks secured?
Webhooks follow the Standard Webhooks specification: an HMAC-SHA256 signature over the id, timestamp and body, so your system can reject forged or replayed messages.
Can we use our own identity provider?
Yes. Staff can sign in through SAML 2.0 or LDAP / Active Directory, and SCIM 2.0 provisions users and groups. Netxol One is also an OpenID Connect provider for your own apps.
Do API calls respect user permissions?
Yes. Every API call checks the same role capabilities as the console, and each ISP only ever sees its own data.
Is Netxol One TM Forum certified?
Netxol One implements 22 TM Forum Open APIs and describes them as ODA components. TM Forum conformance testing is planned; we do not claim certification yet.
Build on live data. Keep your records portable.
Sync subscribers and invoices to your data warehouse, feed alarms into your NOC tool, open tickets from your call-centre software, or build your own subscriber app on the same APIs as the Netxol portal.