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.
