question

adcdc1183 avatar image
adcdc1183 asked ·

API authentication using other extension

Hi, We are trying to authenticate RC credentials using the API. Our RC account has 2 extension numbers. Using the first extension, we are able to authenticate the credentials but using the other one, it resulted to a bad request: HTTP/1.1 400 Bad Request Server: nginx/1.8.0 Date: Fri, 23 Sep 2016 10:30:04 GMT Content-Type: application/json;charset=UTF-8 Content-Length: 49 Connection: keep-alive RCRequestId: b106d9be-8178-11e6-b3aa-005056979a38 RoutingKey: IAD01P08PAS01 Content-Language: en X-AGW-Host: sjc01-c01-agw01.c01.ringcentral.com { "message" : "Bad Request", "errors" : [ ] } Anybody knows what is wrong? We are able to login successfully using that other extension in the Ringcentral site with the same password entered as to the API.
aaa
1 |1000 characters needed characters left characters exceeded

Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.

1 Answer

· Write an Answer
benjamin-dean avatar image
benjamin-dean answered ·
I recommend creating a Developer Support case, and in the case provide the following information please:

1. Your RingCentral Main Company Number
2. Your RingCentral Sandbox Account Main Company Number
3. The Users Extension information for both users (the one that works and the one that does not work)
4. The API Request code you are using to authenticate (and any SDK language/version references if you're using one)
5. Your API Keys (App Key, App Secret)
6. Your Application Name and ID
Share
1 |1000 characters needed characters left characters exceeded

Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.