ICTBroadcast SP Edition Now Includes REST API at No Extra Cost

If you run an ICTBroadcast SP Edition deployment, the REST API is now part of your base license. We’ve folded it into the SP Edition by default, so service providers and ITSPs can integrate any CRM, billing system, or in-house dashboard without paying for a separate API addon. The change applies to all SP Edition installs from May 2026 onward, and existing customers get the upgrade at no charge.

What Changed

Until last week, the REST API was a paid module — an extra you’d add to an SP Edition license when you needed programmatic access. That setup made sense in earlier versions, but most SP Edition customers ended up needing the API anyway. CRM sync, custom client portals, automated provisioning, real-time campaign reporting — almost every meaningful ITSP build path runs through the API at some point.

So we made a decision: stop charging for something nearly every customer needs. Effective today, the REST API is part of the SP Edition core. You don’t need to buy it separately, you don’t need to enable it from an addon menu, and you don’t pay anything additional to use it.

What the REST API Lets You Do

The REST API exposes ICTBroadcast’s three core resource classes — API_User, API_Contact, and API_Campaign — to any external system that can speak HTTP. With these you can:

• Provision new tenant accounts from your billing system the moment a customer signs up
• Sync contacts in and out of your CRM without manual CSV exports
• Start, stop, and monitor campaigns from a custom client dashboard
• Pull campaign results and call summaries into BI tools or reporting pipelines
• Manage user extensions and DIDs as part of your provisioning automation
• Trigger campaigns from external events — a form submission, a CRM workflow, a webhook

The REST API is the bridge between ICTBroadcast and the rest of your stack — CRMs, billing portals, custom dashboards, and BI tools.

Why We’re Bundling It

Honestly? The addon model created friction that nobody asked for. A customer would buy SP Edition, plan their first integration, then hit a paywall on the one thing they needed to actually start building. We’d quote the addon, they’d approve it, we’d enable it — three days lost on a rounding-error line item.

For service providers especially, the API isn’t a premium feature. It’s table stakes. You can’t realistically run a multi-tenant call center business without programmatic provisioning. Charging for something that’s effectively required to operate the product was the wrong call, and we’re correcting it.

What This Means for Existing Customers

If you’re already on SP Edition with the REST API addon, you’ll see the line item drop off your next renewal. If you’re on SP Edition without the addon, you can start using the API immediately — no upgrade, no paperwork, no support ticket. Your existing license already includes it.

The endpoints, authentication scheme, and request/response shapes are unchanged. Anything you’ve built against the API in the past keeps working as-is. If you’re new to the API, the documentation walks through every available call: see Using REST API to integrate ICTBroadcast with third-party applications for endpoint examples and REST API for CRM integration for CRM-specific patterns.

SP Edition vs Enterprise Edition — API Access

One question that comes up: what about Enterprise Edition? Different story. The REST API isn’t part of Enterprise Edition at all. It’s never been bundled, and there’s no addon to add it. If you need programmatic access to ICTBroadcast, the only way to get it is on SP Edition.

For most enterprise customers running ICTBroadcast inside a single organization, that’s a non-issue. The built-in admin UI covers their workflows. But if your roadmap includes CRM sync, custom dashboards, or any kind of automation that reaches ICTBroadcast from outside, you’ll need to move up to SP Edition. Talk to the team about an upgrade path before you start designing around it.

For a side-by-side of what each edition includes, the Pricing & Packages page has the current feature matrix.

API calls can be triggered from inside the IVR designer — useful for real-time CRM lookups during a live call.

Getting Started

If you’ve never touched the API before, the fastest path is:

1. Log into your SP Edition admin portal
2. Open the API documentation from the admin menu — every endpoint is listed with sample requests
3. Generate your API credentials from the user profile
4. Hit a simple endpoint like User_Get or Campaign_Status from curl or Postman to confirm access
5. Start building against your CRM, billing system, or whatever you’re integrating with

For deployment guidance and ITSP-specific setup, the Become an ITSP with ICTBroadcast SP Edition walkthrough covers the full architecture.

Frequently Asked Questions

Is the REST API really free now with SP Edition?

Yes. As of May 2026, the REST API is included in every SP Edition license at no additional cost. There’s no longer a separate addon to purchase or enable.

Do I need to upgrade my existing SP Edition install?

No. The API is already part of the SP Edition codebase. If you have an active SP Edition license, you can start using the API today without any installation or upgrade step.

What if I already paid for the REST API addon?

Existing addon line items will be removed from your next renewal cycle. You won’t be charged for the API again. If you have questions about your specific account, raise a support ticket via the customer portal.

Does this apply to Enterprise Edition too?

No. The REST API is not available on Enterprise Edition at all. It is not bundled, and there is no addon to enable it. If you need API access, you will need to switch to SP Edition. Open a ticket if you want to discuss an upgrade path.

Where’s the API documentation?

API endpoints, request formats, and integration examples are documented at the REST API integration guide. The full list of API functions includes user creation, contact management, campaign control, and reporting endpoints.

Can I integrate ICTBroadcast with my existing CRM?

Yes. The REST API supports integration with any CRM that can make HTTP requests — SuiteCRM, SugarCRM, Vtiger, EspoCRM, custom CRMs, all of them. See the CRM integration guide for patterns and example code.

Related Resources

• Pricing & Packages — full SP Edition feature matrix
• REST API integration guide
• REST API for CRM integration
• Become an ITSP with SP Edition
• Full ICTBroadcast feature list

Questions about the change or about API integration patterns? Open a ticket and one of the engineering team will get back to you.