Hi, we'd like to make some calls to the ZenDesk API, to let our users create some tickets directly on our agents dashboards.
Historically, we used to give the possibility to our customers to create a bug ticket on our support website platform, but nowadays we'd like to change a bit the workdflow and add the possibility for them to create the tickets directly through our app (it's a game).
I've managed to make some calls by requesting the Requests API, but not the Tickets API.
On our support site, users are not forced to log in, they can just fill the forms, give ther mail address, and the system manages to create a ticket right away. Later, the user has to verify his mail. That's one of the classical way of doing I guess.
Through our game code, the tickets route seems to be requiring the users to be connected (those calls are not accessible if not connected it seems). As we don't want them to be connected to zen desk, for many reasons, I've checked the possibilities to create tickets anonymously, and it seems the only way of doing so is using the Requests API ?
With requests, I've managed to create a ticket and
- if the mail of the user is already registered, the ticket is automatically created
- if it's a new user, it falls into suspended_tickets
So far so good I think. But there are two or three things we didn't manage to achieve or didn't understand.
- First of all : is using requests api the proper way of doing things ?
- Creating a ticket that way, it seems that the flag is_public is automatically set to false, which is a huge problem because users can't see their requests/tickets on the web site. Even forcing it to true in the comments doesn't seem to do the trick...
- We also didn't manage to force the language of the request, setting a "Accept-Language" header does not work.
- Last thing, and the most difficult to explain : we'd like to have access to the api/v2/ticket_fields to avoid rebuilding a version of our game everytime those fields change. At runtime, we can access api/v2/ticket_forms, but not api/v2/ticket_fields, which seems to be accessible only when logged in. Is there a workaround for that ?
Thanks for your help.