Question

500 status code returned from restapi/oauth/token

  • 9 November 2015
  • 2 replies
  • 3244 views

  • Anonymous
  • 0 replies
curl -i  https://platform.devtest.ringcentral.com/restapi/oauth/token -d grant_type=password -d username=XXXXX -d password=XXXX -H 'Authorization: Basic XXXX' -H 'Accept: application/json'  HTTP/1.1 500 Internal Server Error
Server: nginx/1.6.3
Date: Mon, 09 Nov 2015 01:43:36 GMT
Content-Type: application/json; charset=UTF-8
Content-Length: 119
Connection: keep-alive
Set-Cookie: RCRoutingInfo=deleted; Expires=Thu, 01-Jan-1970 00:00:01 GMT; Path=/
RoutingKey: SJC11P01PAS01
X-ERROR-ID: fe3a7b58-9b8c-4f0e-b6ec-71dddf716e73
X-REQUEST-ID: 97625
Content-Language: en
{
  "message" : "Internal Server Error. Consult RC Support.",
  "eventId" : "fe3a7b58-9b8c-4f0e-b6ec-71dddf716e73"
}

Exactly same request was sent before, and returned a meaningful response (access toke, refresh token etc)


2 replies

This could have been a hiccup, myself and others on the team have tested this and we've not received any 500 errors.

As long as you're following the documentation here: https://developers.ringcentral.com/api-docs/latest/index.html#!#Authentication.html you should be fine.

I'm going to mark this as answered for now, but if you experience this in the future...let us know.

It may happens in case the ringcentral oauth server is down when you were hitting the API. Else this type of exception is very rare to occur. Maybe you had hit during a down-time

Reply