The custom ticket status id of the ticket See Setting custom field values in the Tickets doc The ids of users currently CC'ed on the ticketĬustom fields for the request. If true, end user can mark request as solved. The id of the assignee if the field is visible to end users Requests are represented as JSON objects with the following properties: ![]() See Status (legacy) and Custom Ticket Status in Tickets JSON Format For example, a GET request to only returns tickets for the Omniwear brand, even if Omniwear is the default brand. In the API path, the brand is specified by the subdomain. It doesn't return all tickets in the account. If you have multiple brands in your account, the Requests API only returns tickets for the brand specified in the API path. See Understanding how Multibrand works in your account in the Support Help Center. On the Enterprise plan and above, a Support account can have more than one brand. See Create Request below.Īdmins and agents have all the permissions of end users and anonymous users. These anonymous requests have a rate limit of 5 requests per hour. See Verifying a user's email address in the Support Help Center.Īnonymous requests are supported for ticket creation but can be disabled by administrators. The problem is flagged by the API with a 403 response. Note: An end user won't be able to view their requests if the end user added an email identity (an email address associated with a Zendesk profile) after September 17, 2017, and didn't verify the email address. See Requests in Supported Endpoints in Side-loading. You can sideload some resources with requests. Use this API to let end users view, update, and create tickets they have access to. ![]() End users can only see public comments and certain fields of a ticket. A request is an end user's perspective on a ticket.
0 Comments
Leave a Reply. |