

These steps are not necessarily in a fixed order. Optionally add notes to the order to communicate with Bandwidth.Optionally upload supporting documents.
PORT SOURCES LIST PORTING KIT UPDATE
Optionally update fields in the port-in.Create the port-in order, possibly in DRAFT state.Request a FOC date, or default to the earliest estimated FOC date.Check if the numbers are portable and can be ported together.To create and manage a port-in (regular or toll free), these are the basic steps: Checking Portability for Toll Free Numbers.Checking Portability for Regular Numbers.You can find more information about rules for which numbers can port together in a stand-alone port-in in the sections called one person is financially responsible for the numbers on the losing account) A single person has the ability to authorize the port (i.e.They are in service with the losing carrier or controlling RespOrg.They are hosted by the same losing carrier or controlling RespOrg prior to the port-in.In general, numbers can be ported together if they meet the following criteria: This same API is used for porting both regular and toll free telephone numbers, although unlike bulk port-ins, regular and toll free numbers cannot be mixed together in a stand-alone port-in. The /portins API is used to create and manage a single port-in order for a set of telephone numbers that are portable and can be ported together.
