Parameter [brandId] is invalid

  • 1
  • Problem
  • Updated 2 years ago
When I send a request to https://platform.ringcentral.com/restapi/oauth/token, I receive the following:

{
  "error" : "invalid_client",
  "error_description" : "Access to account denied.",
  "errors" : [ {
    "errorCode" : "OAU-101",
    "message" : "Parameter [brandId] is invalid",
    "parameters" : [ {
      "parameterName" : "brandId",
      "parameterValue" : "3610"
    } ]
  } ]
}

The data sent in request body is:

access_token_ttl=&refresh_token_ttl=36000&grant_type=password&username=***********&password=*********************&extension=

Username and password are correct, when I try with wrong password returned error is different (Invalid resource owner credentials).

The phone number used is not from our own account, it's our client's

When I try to login using our own number, it works just fine.

App name is "1CRM RingCentral Connector", and application type is set to "Public"
Photo of Andrey Demenev

Andrey Demenev

  • 160 Points 100 badge 2x thumb

Posted 2 years ago

  • 1
Photo of Anton Nikitin

Anton Nikitin, Official Rep

  • 2,522 Points 2k badge 2x thumb
I assume that your app is not authorized to work with RC Canada brand. By default all apps are only enabled for RC US so they can used only by RingCentral US customers. But I assume we can fix it for your app. Stay tuned.
Photo of VB

VB, Official Rep

  • 1,290 Points 1k badge 2x thumb
Could you please try again. I have updated "1CRM RingCentral Connector" app adding RC Canada brand. 
(Edited)
Photo of Andrey Demenev

Andrey Demenev

  • 160 Points 100 badge 2x thumb
Anton, VB, thank you! Now I am able to login. 

What is the reason for disabling Canada by default?

We also have many clients using our software in UK and all Europe, and some in Australia and Asia. If they decide to use RingCentral integration, we'll have this same problem again.
Photo of Benjamin Dean

Benjamin Dean

  • 8,602 Points 5k badge 2x thumb
I have submitted a ticket to Engineering to mass-enable all appropriate accounts, and to include enabling this feature as part of provisioning for any new on-boarding customers.