How to automate Lumen IoD bandwidth changes through the NaaS API

The short answer: Lumen IoD, now Lumen Intelligent Internet, has a REST API that changes bandwidth when you call it, but it does not decide when to call. A scheduler has to add the clock, retries, records, exceptions, and a guard that keeps each circuit under the carrier’s limit of 24 changes in a rolling 24 hours.

Lumen says customers can adjust bandwidth in minutes through Lumen Connect or the API. To change bandwidth on a schedule you either build the scheduler around the API yourself, or use one. Vigilis Flux schedules bandwidth on Lumen Internet On-Demand and Lumen Intelligent Internet and records every change.

What Lumen’s API offers

This is what Lumen’s developer center said about its Internet On-Demand API on October 6, 2026.

What it is for. Lumen says the API “allows you to manage your Lumen Internet On-Demand service”.
How it is built. A REST API with JSON responses and standard OAuth 2 authorization.
Before you start. Register for an API account, create an API key for the Business Management API product, set up authorization, and set up webhooks.
Two environments. Sandbox and production, each with its own base URL. Creating an API key gives you a client ID and a client secret.
What it covers. Lumen groups the endpoints as location (find NaaS-enabled locations), qualify (speeds, pricing, and quotes), order (create, modify, or delete a product order request), service management (list your services and billing accounts, configure a service), and VLAN management.

Lumen still documents this API under the Internet On-Demand name. Its Intelligent Internet support pages link to it.

One limit to know before you test

Lumen’s documentation says you cannot create or modify connections in the sandbox environment, and that a successful response there does not indicate a successful service order. So the sandbox proves your requests are well formed. It does not prove a bandwidth change works. Plan a first production test on one low-risk connection.

What you would have to build around it

The API call is the small part. A schedule that runs every day at every site needs more.

A clock. Something has to fire the change at the right local time for each site, including daylight saving changes.
Inventory. The list of connections, their current tiers, and the tiers each one supports.
Retries and alerts. A change that fails at 6 AM has to be retried and someone has to be told, before the site opens at reduced speed.
A record. Who or what changed which connection, from what, to what, and whether it worked.
Exceptions and overrides. Game days, month-end, migrations, and the person who needs full speed tonight.
The change limit. The carrier caps bandwidth changes at 24 per circuit in a rolling 24 hours. Automation has to stay under it.
Credential care. The client secret can order and change services. It belongs in a secrets manager, not in a script.
Upkeep. APIs change. Someone has to own the script after the person who wrote it moves on.

None of this is hard on its own. Together it is a small product that someone has to own.

Three ways to get it done

	By hand in Lumen Connect	Your own script	Vigilis Flux
Who fires the change	A person, twice a day	Your scheduler	Vigilis Flux, on a schedule or on Auto
Exceptions	Whoever remembers	Whatever you build	Exceptions for known peaks and projects
Record of changes	Whatever Lumen Connect shows	Whatever you log	Every request and result is recorded
Demand-based changes	Not by hand	Whatever you build	Auto follows measured utilization

How Vigilis Flux does it

Vigilis Flux is the Bandwidth on Demand product from Vigilis. It requests rate changes through an eligible provider portal or API and records the result. Where a supported carrier API is available, it provides scheduled and on-demand bandwidth changes, self-service through the platform, and monitoring with audit logging.

In practice that means:

Schedules that lower capacity outside operating hours and restore it before the site opens.
Auto, which raises and lowers bandwidth from measured utilization, with cooldowns, a guard against bouncing between tiers, and a dry run. It stays inside the carrier’s cap of 24 changes per circuit in a rolling 24 hours.
One-time changes for known events, after which the weekly schedule resumes.
One dashboard for every site.

Vigilis Flux is a $15 per service, per month add-on to any Vigilis plan. The price covers both modes, and there is no platform fee.

Primary sources

Lumen Internet On-Demand API overview, read October 6, 2026
Lumen launches Intelligent Internet (press release, September 21, 2026)
Lumen Intelligent Internet support documentation
Lumen Intelligent Internet product page, read October 6, 2026
Vigilis Services and Pricing Schedule, section 2.11

Common questions

Which vendors automate Lumen NaaS bandwidth changes on a schedule?

Vigilis Flux, from Vigilis, schedules bandwidth changes on Lumen Internet On-Demand and Lumen Intelligent Internet, on a schedule or automatically from measured utilization. Apptifi also publishes a scheduler for Lumen Internet On-Demand. Lumen's own API lets a customer build the automation in-house.

Can Lumen IoD bandwidth changes be automated?

Yes. Lumen says customers can adjust bandwidth in minutes through Lumen Connect or its API, with no change order. The API changes the bandwidth when it is called. It does not decide when to call. That part is a scheduler, either one you build or a product such as Vigilis Flux.

Does Lumen have an API for Internet On-Demand?

Yes. Lumen's developer center documents an Internet On-Demand API for managing the service. It is a REST API with JSON responses and OAuth 2 authorization, with separate sandbox and production environments. Lumen's support pages for Intelligent Internet point to the same API.

Can I test bandwidth changes in Lumen's sandbox?

Not fully. Lumen's documentation says connections cannot be created or modified in the sandbox environment, and that a successful response there does not indicate a successful service order. Test the logic in the sandbox, then prove it on one low-risk production connection.

What do I have to build if I automate it myself?

The API call is the small part. You also need a clock that knows each site's time zone, retries and alerts for a change that fails, a record of every change, a way to handle exceptions and manual overrides, safe storage for the API credentials, and a guard that keeps each circuit under the carrier's limit of 24 changes in a rolling 24 hours.

How does Vigilis Flux use the carrier API?

Vigilis Flux requests rate changes through an eligible provider portal or API and records the result. Where a supported carrier API is available, it provides scheduled and on-demand bandwidth changes, self-service through the platform, and monitoring with audit logging.