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.
-
- Ideas
- Developers
- Partners
- Users
- News & Announcements
- RingCentral App (Desktop)
- Integrations
- Features
- Services and Products
- Fax
- Billing & Invoicing
- Analytics & Reporting
- Announcement & Message Only Extensions
- Audit Trail
- Call Log
- Call Quality
- Call Recordings
- Caller ID/CNAM
- Canada RingCentral Support
- Conference Calling
- Desk Phones
- Employee Discussions (Private)
- Getting Started
- Global Office
- HUD - Heads Up Display
- IVR
- Limited Extensions
- Live Reports
- Multi-Site
- Outlook Integration
- QoS Tool
- RingCentral Channel Partners (Private)
- RingCentral Contact Center
- RingCentral Engage Digital
- RingCentral Engage Voice
- RingCentral Meetings
- RingCentral Phone (desktop)
- RingCentral Rooms
- RingCentral Webinar
- RingCentral app (Glip)
- SMS/Text Messaging
- SSO (Single Sign-On)
- Shared Lines
- UK RingCentral Support
- User Community
- User Interface Improvements
- User Settings - Messages Tab
- User Settings - Voicemail
- User Topics
- Training Resources
- Sign in