500 internal server error posting to deployments API

I've been trying to implement Deployment Tracking using the API directly and am receiving a 500 Internal Error response when I POST to it. The following is an example of the raw request (keys replaced for obvious reasons):

POST /deployments?authToken=token HTTP/1.1 Host: app.raygun.io Cache-Control: no-cache

{ apiKey = 'key', version = '1.0.1481' }

Is there a problem with the API, or am I doing something wrong?

Hi David,

I saw those errors come in just before. You've got an error in your JSON - you should be sending that through as

{ apiKey: 'key', version: '1.0.1481' }

: instead of = basically.

Best regards, Jamie

Haha - the downside to polyglot programming is context switching :) Thanks

One other issue - the Deployments Beta page appears to be blank, and there are a couple of Javascript errors occurring:

Uncaught TypeError: this.ui.loading.removeClass is not a function Uncaught TypeError: this.ui.loading.addClass is not a function

So I can't currently see any deployments...

Ouch - we just pushed a change to that, must be the new graph playing up. Will jump on that now.

Alright should work now - we had a race condition in one of the event triggers that caused the UI to update before it had rendered. Of course it didn't get triggered in any of my Raygun applications. Let me know if you run into any more problems.

The page seems to be working now Jamie, although the "Recent deployments" area (graph?) is blank. This might be by design? If it is it might be nice to show something there stating that no exceptions have happened or something as it looks a bit weird.

Thanks for the fast responses!

Can you try refreshing the page, without switching tabs or minimising the window? There's an odd bug in the charting library we use that causes the graph to be blank if the render animation completes while the tab is offscreen.

If that's what is going wrong, I'll try come up with a work around tomorrow. I wasn't sure that anyone else would refresh the page then tab away like I tend to do, but it's on my list of known issues.

The graph is coming up now, I'm not sure what changed it just started appearing. Apologies I couldn't reproduce the prob!