News & Announcements User Community Developer Community

Welcome to the RingCentral Community

Please note the community is currently under maintenance and is read-only.

Search
Make sure to review our Terms of Use and Community Guidelines.
  Please note the community is currently under maintenance and is read-only.
Home » Developers
Receiving a CMN-211 / HTTP 503 obtaining an OAuth token from DevTest environment
Tags: authentication
Apr 25, 2016 at 9:16am   •   2 replies  •  0 likes
benjamin-dean

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?

2 Answers
answered on Jun 25, 2019 at 2:58am  

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


 0
answered on Apr 25, 2016 at 9:18am  
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.

 0



A new Community is coming to RingCentral!

Posts are currently read-only as we transition into our new platform.

We thank you for your patience
during this downtime.

Try Workflow Builder

Did you know you can easily automate tasks like responding to SMS, team messages, and more? Plus it's included with RingCentral Video and RingEX plans!

Try RingCentral Workflow Builder

PRODUCTS
RingEX
Message
Video
Phone
OPEN ECOSYSTEM
Developer Platform
APIs
Integrated Apps
App Gallery
Developer support
Games and rewards

RESOURCES
Resource center
Blog
Product Releases
Accessibility
QUICK LINKS
App Download
RingCentral App login
Admin Portal Login
Contact Sales
© 1999-2024 RingCentral, Inc. All rights reserved. Legal Privacy Notice Site Map Contact Us