12 comments

0

Shajith Chacko
September 14, 2012 21:40

Put "public" in quotes to hint that you are using it as a string. JSHint should allow that.

When making AJAX calls to your own zendesk, you should use relative URLs. This is a deficiency in the way we determine whether to proxy your AJAX request or not, but you can get around that for now by using relative URLs.

I would suggest trying going to the (full) URL in your browser. If that also returns a 403, it's likely that your current user doesn't have access to that ticket. If it doesn't, I'd try again as an AJAX call from the console: jQuery.ajax({ url: '/api/v2/tickets/5.json' }) . If that returns a 403, then I'll investigate why AJAX calls don't have access to that URL. If that returns a 200, though, then the problem is in the app and you should submit a ticket and attach the app source.

0

Jeff Tanner
September 16, 2012 17:18

Hi again

I tried both suggested tests, and I had experienced no 403 problems.

Using Chrome, I logged into my Zendesk desktop

Was able to view ticket's JSON object using full-path

ran jQuery.ajax({ url: '/api/v2/tickets/5.json' }) from Chrome console using root-path, was able to see JSON object