Home » Support » Telligent Evolution Platform » Telligent Community » Discussions » Debugging REST API

Debugging REST API

Open Support Ticket

Call Support:
Direct: (214) 420-1337
Toll Free: (877) 522-6334

Monday through Friday
8 a.m. to 6 p.m. Central (GMT-6)

Join our Community
Details
  • 3 Replies
  • 1 Subscriber
  • Postedover 1 year ago
Options

Debugging REST API

This question is not answered
ckuhlow
Posted by
on Thu, May 17 2012 5:08 PM

Is there any way to debug the REST API calls?  I making a call to grab permissions associated with a particular media gallery and I receive a generic 500 internal server error with no details.  Any way to get more info from the exception so that I can better troubleshoot?  I get nothing in the exception log.

Also, it works in our development environment but not in production for some reason.  So I'm not positive what's going on.  Other calls to the API work, just not this one, so it's not a bad API key.
All Replies
  • Liam Kenny
    Posted by
    on Fri, May 18 2012 1:00 PM

    I have had the similar issues trying to debug the API calls.  My solution was to rebuild the calls in a trimmed down version as a console app in Visual Studio.  This allowed me to insert breakpoints where ever needed and see exactly what was going to the call and what was coming back.  it was pretty effective for my needs.  if you hit me up out of the forum, i can send you a sample console app to give you an idea of what i did.
  • Alex Crome
    Posted by
    on Fri, May 18 2012 2:06 PM

    You can use Fiddler, or another network traffic capture tool, to capture the HTTP requests & responses for your API calls.

    If you're getting a 500 server error, debug teh same way you'd debug an error message on the server - look in the exception logs for a stack trace.
  • ckuhlow
    Posted by
    on Fri, May 18 2012 8:23 PM

    I figured it out.  The IIS server logs and Telligent logs weren't logging anything so I ended up doing what Liam had suggested and created a console app with breakpoints and was able to get the exception that way.