Skip to main content

When I tried to obtain an access_token from the DevTest/sandbox environment I received a HTTP 503 response / CMN-211 response instead of the expected access_token and a 200 response for the following request:

POST /restapi/v1.0/oauth/token

HOST: https://platform.devtest.ringcentral.com

HTTP Headers:

  • Content-Type: application/x-www-form-urlencoded;charset=UTF-8
  • Authorization: Basic <BASE64_ENCODED_API_KEYS>
  • Accept: application/json

POST Body:

grant_type=password&username=<RC_USERNAME>&password=<RC_PASSWORD>&extension=<RC_EXTENSION>

NOTE: I did replace the values in tags above with actual values

The response I received was:

{ 

  "errorCode": "MaintenanceMode",

  "message": "Service is overloaded, please retry later",

  "errors": [

    {

      "errorCode": "CMN-211",

      "message": "Service is overloaded, please retry later"

    }

  ]

}

Is the devtest environment in Maintenance mode, or am I doing something incorrectly?

Figured out what the problem is. The RingCentral OAuth route does not utilize the version string in the path.

The path I was providing was invalid according to all the documentation in RingCentral. 

If I remove the "/v1.0" from the PATH being used, then I receive a HTTP 200 response and the expected access_token.

Sharing this in case other developers experience this as well and to help save them some time.

Yes, the correct url contains /restapi/oauth/token and not any version v1.0

If you check the document here https://developers.ringcentral.com/guide/authentication/password-flow

You will find the correct way of calling it

Reply


Terms & ConditionsCookie settings