News & Announcements User Community Developer Community

Welcome to the RingCentral Community

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

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
Help debugging a CMN-101 error
Tags: rest api
Oct 4, 2023 at 12:32pm   •   0 replies  •  0 likes
Byrne Reese

The CMN-101 error is a relatively generic error thrown by the RingCentral platform when it receives a request parameter that it doesn't understand, anticipate, or that might be transmitted in error. Resolving the error requires the developer to carefully inspect their request, and compare it to the API Reference for that endpoint to ensure that the request is being populated correctly. The error looks like this:

     "errorCode": "InvalidParameter", 
     "message": "Parameter [uri] value is invalid.", 
     "errors": [ 
         { "errorCode": "CMN-101", 
           "message": "Parameter [uri] value is invalid.", 
           "parameterName": "uri" } 
     "parameterName": "uri" 

The best guidance we can offer when trying to troubleshoot this problem, which often relates to one isolating the issue with a specific request parameter is the following:

  • Remove all optional request parameters from your request. Transmit only the required fields and the fields you are customizing.

  • Add optional fields back one-by-one until you find the offending request parameter. Note however, that the error message should in theory identify the request parameter that is "broken."

Common cause for the CMN-101 error We often see this problem with developers using the API Reference to try-out an API or endpoint. This tends to happen when using the API Reference as it may populate values for request parameters based on some pre-assigned default value. Obviously, default values should not trigger an error, but that cannot be guaranteed in all circumstances, especially when the default value is there to illustrate one possible hypothetical value, e.g. to show how to format a value for example. If the above situation applies to you, and you find the API Reference is causing an error you did not expect, please let us know so that we can address the issue for future developers.

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

Developer Platform
Integrated Apps
App Gallery
Developer support
Games and rewards

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