The Branded Communication API offers a single point of entry into First Orion's INFORM solution, 1/3 of United States devices. The API is structured under the following top-down hierarchy:
A Business is represented in the BC API as an object containing the information needed for business registration. This includes information relevant to legal identification, addresses, contacts, and the context of the business, as shown below:
An API user can create, update, and get information about businesses via the Branded Communication Business endpoints.
Note: Only users with Partner permissions may access the endpoints used to create and manage businesses via API.
There are five business endpoints aside from the primary Business endpoint used for creation and management:
Below are the values representing information required for the business industry and employee count information submitted during business registration.
Service grants represent, and gate access to, the different distribution paths through which your business is sending branded calling. This is present on the business object.
|"CT"||Your business numbers are being registered for First Orion to mitigate scam tagging on the T.Mobile network. All businesses have this added by default, and is the base requirement for having access to the branded calling platform.|
|"CE"||Branded calling numbers registered to a callername in an INFORM program are being distributed through the T.Mobile network.|
|"ATT"||CE service with additional ATT network distribution (requires CE grant)|
|"VZW"||CE service with additional Verizon network distribution (requires CE grant)|
*require extra authentication from First Orion Support
|8||10,001 + employees||9|
A Business Unit is represented in the Branded Communication API as simply its name. The successful activation of a business is required for Business Unit creation and management. Creating a business unit is a required step before program creation. There is one Business Unit endpoint used to create and manage the information associated with a business unit.
A Program is represented in the Branded Communication API by the purpose of the program, the estimated daily call count, and its schedule. There is an optional flag on the program object to allow for the use of PAIRED pre-call authenticated delivery.
There are three endpoints used to manipulate the information used in the Program Object:
|EN||Informational / Notification|
|S6||Do Not Originate|
|2||Up to 100||2|
|3||Up to 500||3|
|4||Up to 1,000||4|
|5||Up to 5,000||5|
|6||Up to 10,000||6|
|7||Up to 25,000||7|
|8||Up to 50,000||8|
|9||Up to 100,000||9|
|10||Up to 250,000||10|
|11||Up to 500,000||11|
|12||Up to 1,000,000||12|
|13||More than 1,000,000||13|
Branded Communication Delivery Channels represent how the end call will be displayed and to what channel(s) the calls will be distributed.
The Phone Number object is represented similarly to Branded Communication programs with the addition of the relationship object used to map the phone number to associated businesses and programs:
Call Purpose codes are the same as program call purpose codes.
There are three endpoints used to manipulate the information and entities associated with a phone number:
Pre-Call authentication is used to push the content to be delivered by a Pre-Call program ahead of the phone call. This can be used for Inform and Engage programs. The pre-call object is represented in Branded Communications by the services to be used as well as the length of time the assets will be associated with the phone numbers specified.
The pre-call push API consists of two endpoints used to push the information for either an Inform or Engage branded call with pre-call authentication.
Updated 24 days ago