Smarter Voice Networks Made Easy with SBC API Integration

ProSBC is a high-performance, carrier-grade Session Border Controller (SBC) trusted by service providers worldwide. Its strength lies in a powerful scripting engine at the core of every ProSBC Application Programming Interface (API). This engine leverages over 100 call parameters to create intelligent, highly customizable call flows. When these scripts interact with external services—such as fraud detection platforms, routing engines, or analytics tools—they become dynamic API integrations that enhance real-time decision-making.

Whether you’re building custom routing logic, enabling fraud detection, or implementing compliance tools like STIR/SHAKEN, ProSBC APIs give you the flexibility to connect your Session Border Controller to the rest of your telecom stack.

Overview of ProSBC API Features

API Feature

Function

Use cases

Resources

REST API Integration

Enables external systems to interact with ProSBC using HTTP methods (GET, POST, PUT, DELETE) for call decisions, provisioning, and monitoring.

Fraud Prevention, Branded Calling, Call Reputation, SBC Provisioning, Data-Driven Call Routing

STIR/SHAKEN API Support

Verifies and signs calls using REST or SIP Identity headers for caller authentication and regulatory compliance.

STIR/SHAKEN Compliance, Branded Calling

Routing Script Engine

Uses Ruby-based scripting to define custom call routing logic in the browser without compilation.

Advanced Routing, Service Chaining

CNAM, LNP, Toll-Free Lookup

Performs external lookups via REST API to retrieve caller name, number portability status, and robocall analytics.

LNP Routing, CNAM Delivery, Toll-Free Call Handling

Real-Time Billing & CDR

Generates detailed CDRs and supports billing event triggers for integration with external charging systems.

Billing

ProSBC API Solutions

API Feature

Function

Use cases

Resources

REST API Integration

ProSBC supports REST API integration during SIP call processing, enabling interaction with external systems in real time. This functionality is driven by ProSBC’s scripting engine, which allows for precise control over when and how API calls are executed using more than 100 available call parameters, such as caller ID, dialed number, or SIP headers.

This approach allows service providers to implement use cases like fraud prevention, branded calling, call reputation analysis, SBC provisioning, and data-driven call routing. Because the API logic is handled within the script, integration is highly flexible and can be tailored to meet specific operational or business requirements.

API calls are made during the signaling phase of the call, ensuring that decisions are made quickly and do not affect media quality. The result is a scalable, reliable way to enhance call handling with external data and services.

Figure: Example of a network architecture of ProSBC API Integration​

Use Cases: Fraud Prevention, Branded Calling, Call Reputation, SBC Provisioning

“REST APIs and ProSBC“ webinar recording: REST APIs and ProSBC

STIR/SHAKEN API Support

ProSBC integrates with STIR/SHAKEN authentication services using REST or SIP Identity headers. It signs and verifies calls to prevent spoofing and comply with regulations. Prebuilt scripts simplify deployment with common platforms.
Use Cases: STIR/SHAKEN Compliance, Branded Calling
More details: STIR/SHAKEN Integration

Routing Script Engine

ProSBC’s routing script engine uses the Ruby programming language to create flexible, browser-based call routing logic without compilation. It supports built-in scripts for use cases like least-cost routing, round-robin, SIP trunking, and over-subscription, and allows providers to modify routing behavior easily through the web interface.
Use Cases: Advanced Routing, Service Chaining
More details: Routing Scripts

CNAM, LNP, and Toll-Free Lookup

ProSBC integrates with services like TransNexus ClearIP to perform CNAM, LNP, and toll-free number lookups via REST API during call setup. The SBC sends call data to ClearIP, which returns caller name, porting status, and robocall analytics that ProSBC can use to adjust routing or caller display. This enhances call accuracy, fraud prevention, and caller trust in real time.
Use Cases: LNP Routing, CNAM Delivery, Toll-Free Call Handling
More details: CNAM and Robocall Analytics with ClearIP

Real-Time Billing and CDR Integration

ProSBC generates customizable Call Detail Records (CDRs) and supports external charging triggers. These can be exported or sent via API for billing and reconciliation.
Use Cases: Billing
More details: CDR Configuration

Ready to Get Started With SBC API Integration?

Whether you’re integrating a fraud detection engine, enabling branded calling, or adding advanced routing logic, ProSBC APIs give you the control and flexibility to build the voice services your business needs.


Start ProSBC Trial

Frequently Asked Questions

Session Border Controller API integration empowers service providers to make smarter, real-time decisions by connecting their Session Border Controller to external systems like fraud detection platforms, routing engines, and analytics tools. With ProSBC’s scripting engine leveraging over 100 call parameters, APIs enable dynamic call flows for various use cases, for example, branded calling, STIR/SHAKEN compliance, least-cost routing, and real-time billing. Because decisions are executed during call signaling, providers gain flexibility without sacrificing performance, improving security, compliance, efficiency, and customer trust.

REST API integration improves call handling with ProSBC by enabling real-time interaction with external systems during SIP call processing. Using over 100 available call parameters, such as caller ID, dialed number, or SIP headers, ProSBC can trigger API calls to fraud detection platforms, routing engines, or analytics tools before the call is connected. This ensures smarter, data-driven call decisions without affecting media quality, helping service providers enhance security, optimize routing, and deliver a more reliable calling experience.

API decisions happen during the call signaling phase, so routing, fraud checks, and compliance measures are completed before the call is connected. This ensures security and efficiency without affecting audio quality.