Skip to main content

band portin bulk create

Create a bulk port-in order with a large TN list

Synopsis

Submits a bulk port-in. This is a two-step call under the hood: the API requires an empty template order first (POST /bulkPortins), then the TN list on a second request (PUT /bulkPortins/{id}/tnList). The API then splits the list across multiple child port-in orders (one per RespOrg or carrier group) and validates each TN asynchronously. Use band portin bulk get-tns <id> --wait to poll the validation outcome.

band portin bulk create [flags]

Examples

band portin bulk create --numbers-file ./tns.txt --site 1234 --peer 5678
band portin bulk create --numbers +18005551234,+18885551234 --foc 2026-06-01

Options

--customer-order-id string Customer-supplied order identifier (used as the idempotency key)
--foc string Requested FOC date for the bulk order as a whole (YYYY-MM-DD)
-h, --help help for create
--if-not-exists If a bulk port-in with the given --customer-order-id already exists, return it
--numbers strings TNs to port in, comma-separated or repeated. Either --numbers or --numbers-file is required.
--numbers-file string Path to a file with one TN per line (or comma-separated)
--peer string SIP peer (location) ID for the destination
--site string Site (sub-account) ID for the destination

Options inherited from parent commands

--account-id string Bandwidth account ID (overrides config)
--environment string API environment: prod, test (overrides config)
--format string Output format: json or table (default "json")
--plain Simplified flat JSON output (recommended for scripts and agents)

SEE ALSO