Replies posted by rohit.eddy_old
Hi Mitul,The API team has noted this as a feature enhancement request. We have heard similar requests from others and it is something that I would like to definitely address. This may take a while however, as we are right now focussed on the release of our upcoming v2 APIs which will feature better performance. We will revisit this once the v2 APIs are out and I should be able to give you a more detailed update on this request at that point.
It appears that the Auth header is not being set. It needs to be set explicitly. The information in the following link may prove useful - http://stackoverflow.com/questions/5507234/how-to-use-basic-auth-and-jquery-and-ajax/5507289#5507289
The standard format for authenticating with the API key is to use the format APIKEY:X where APIKEY is your API key and X is a dummy password (There is no password required, but we use a dummy one to maintain the format used when you authenticate via username:password).If that is not working for you, I will need to check with my engineers and get back to you.
Yes you can authenticate with just the API key, the format is the one mentioned in my last post. The format is <api_key>:<dummy_password>. So for example if your API key is "a1jf6t95", you will have to use "a1jf6t95:X" to authenticate where "X" is a dummy password (not your real password).
We have included this API for tickets as part of the new generation v2.0 APIs -http://developer.freshdesk.com/api/#list_all_tickets. The updated_since filter will enable you to get only the tickets that you need. It's still in beta, but you can try it out and see if it meets your needs.
Currently, you cannot create custom fields via API, they need to be created via the portal. Once created, you can create new tickets that contain that custom field.If you are using the API v1, then please follow this guide - https://support.freshdesk.com/support/solutions/articles/205831If you are using API v2 (still in beta) then please look at this guide - https://support.freshdesk.com/support/solutions/articles/216548
We do something similar to what you are requesting for "View a Ticket" i.e when you say "include=conversations" we send additional information along with a ticket. We are currently exploring the possibility of sending some additional info such as resolved, closed, first response, and resolution times. We have not made a decision yet, I will post an update here once we have decided.
Hi Michael,I'm sorry if my reply was not clear. What I meant was that we are looking into providing the fields that you are looking for as optional fields. The mechanism would be similar to include=conversations. Hence, it may look like include=stats and we could send these fields.The reason we went with this model is that we had users complaining that we were sending too much information back with our v1 APIs. With v2, we have decided to adopt a more modular approach, we send the bare minimum and send additional information only when requested to do so.
Join the Community
Sign in to the Community
Social LoginLogin for Freshworks Employees Login with LinkedIn
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.