The Client ID is part of the OAuth process and used by any developer that is using the PhoneBurner API to allow their members to connect the member/s external CRM to the members PhoneBurner account.
For example, If I am the creator of a CRM, and I want to allow my members to use the PhoneBurner power dialer directly from my CRM, I will need to create the integration. PhoneBurner refers to this as an APP.
Once I ,"the CRM", have created the integration using the API, I will need to register this integration with PhoneBurner. Anyone can register their APP/integration with PhoneBurner through this page in their PhoneBurner account:
When I, "the CRM", register a new APP, I provide PhoneBurner with the details about how to communicate with my system and Authenticate the member/s looking to connect the two systems (my CRM and PhoneBurner). Once my APP is registered with PhoneBurner, PhoneBurner will provide me with a Client ID and Client Secret. The Client ID is essentially my APP's Username on the PhoneBurner system. The Client Secret is like a Password (the client id/secret establishes trust between PB and the CRM).
Once I, "the CRM", complete my integration between PhoneBurner and My CRM, I would provide a way for our mutual member/s to grant access for both systems to talk to each other.
If I, "the CRM", am setting up the integration in a way to allow our mutual members to start a dial session directly from my external CRM, this option to Grant Access is usually done when the member starts their first dial-session. The member would be presented with a screen to log into PhoneBurner and then Allow the connection between the 2 systems. Once the connection has been Granted by the member PhoneBurner would provide me with an Access Token that is specific to this members account.
As long as I "the CRM" use this token, PhoneBurner knows I "the CRM" am making API calls on behalf of our mutual member.
This OAuth process is covered here: