Skip to content

Data Flows

Input

NSPS receives event notifications (webhooks) from PortaBilling ESPF via secure HTTPS connections.
Each webhook is generated by the EventSender component and follows the ESPF event structure.

These events contain a set of variables — system-defined fields describing the affected object (account, SIM card, or service) and providing metadata about the event itself.
The composition of these variables depends on the specific event_type.

Typical data received by NSPS includes:

  • Event type — defines the kind of change in PortaBilling (e.g., account status change, SIM update, or service provisioning event).
  • Object identifiers — such as i_account, i_env, or SIM ID, which uniquely identify the related PortaBilling entity.
  • Event metadata — including internal event ID and timestamp indicating when the event was triggered.

Once received, NSPS parses the event, validates its structure, and determines which additional PortaBilling data needs to be fetched for enrichment.

For more information on event types and payload formats, refer to:

ESPF event specification
Details all supported ESPF events and their types handled by PortaBilling.

EventSender configuration
Describes how EventSender generates and delivers webhook events to NSPS.

Event variables reference
Lists all variables available in different ESPF event payloads.

Output

After receiving ESPF event and enriching data from PortaBilling APIs, NSPS forwards it to a connector microservice, which is responsible for synchronizing with an external platform (for example, a CRM, provisioning engine, or monitoring system).

The enriched payload includes all the identifiers and metadata from the incoming event,
along with additional details obtained from PortaBilling (see Account Interface API).

Key components of the enriched output:

  • Identifiers — all IDs from the ESPF payload, such as i_event, i_account, etc.
  • Extended data — account, SIM, and service information fetched through PortaBilling API calls.
  • Context fields — additional attributes or computed values required for proper provisioning in external systems.

The enriched data enables connectors to perform precise and context-aware actions such as:

  • updating user or SIM status in external CRMs;
  • provisioning network services;
  • synchronizing service state with third-party systems.

For more detailed references, see the following sections:

Output Data Structure documentation
Provides the detailed structure of enriched events sent by NSPS to connectors.

Event Types
Explains all possible event_type values for ESPF events.

Headers
Describes additional HTTP headers that NSPS sends to connectors.

Simple example request body of an enriched event 
1
2
3
4
5
6
7
8
9
    {
        "event_id": "3e84c79f-ab6f-4546-8e27-0b6ab866f1fb",
        "data": { ... },
        "pb_data": { ... },
        "handler_id": "wtl-hlr-hss-nsps",
        "created_at": "2025-03-12T16:47:30.443939+00:00",
        "updated_at": "2025-03-12T16:47:36.585885+00:00",
        "status": "received"
    }