The\u00a0 The\u00a0 Double quotes ( The\u00a0 The\u00a0 Zendesk REST APIs require URL encoding for any URL parameter values, including the\u00a0 For example, to submit a search request using a\u00a0 You can sort your search results by field, in ascending or descending order, using the following keyword phrases:<\/p>\n Sorting is available on the following fields:<\/p>\n Using the\u00a0 For API searches, one of the tools you have available for narrowing your search results is the\u00a0 Using the\u00a0 If you instead searched for\u00a0 Using\u00a0 While organizations and groups are properties of the user object, they have their own properties that can be searched as well. The following query allows you search only for organization tags, excluding tags of the same name that may be used in other elements of your Zendesk Support instance such as tickets and forum topics.<\/p>\n To search for a user’s profile data, you have the following two options.<\/p>\n Using the\u00a0 Or, using the\u00a0 For more information about the\u00a0 How the query syntax works The\u00a0query\u00a0string syntax uses the following rules: The\u00a0:\u00a0character is the equality operator. Other operators include\u00a0<\u00a0(greater than) and\u00a0>\u00a0(less than), the minus sign\u00a0–\u00a0(negation), and the wildcard (*) character. See\u00a0Search operators\u00a0in Zendesk help Double quotes ("") are used for search phrases. The search only returns records that contain an exact match of the phrase. … L\u00e4s mer<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-288","page","type-page","status-publish"],"_links":{"self":[{"href":"https:\/\/solarxbike.se\/labbet\/code-snippets\/wp-json\/wp\/v2\/pages\/288","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/solarxbike.se\/labbet\/code-snippets\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/solarxbike.se\/labbet\/code-snippets\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/solarxbike.se\/labbet\/code-snippets\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/solarxbike.se\/labbet\/code-snippets\/wp-json\/wp\/v2\/comments?post=288"}],"version-history":[{"count":5,"href":"https:\/\/solarxbike.se\/labbet\/code-snippets\/wp-json\/wp\/v2\/pages\/288\/revisions"}],"predecessor-version":[{"id":403,"href":"https:\/\/solarxbike.se\/labbet\/code-snippets\/wp-json\/wp\/v2\/pages\/288\/revisions\/403"}],"wp:attachment":[{"href":"https:\/\/solarxbike.se\/labbet\/code-snippets\/wp-json\/wp\/v2\/media?parent=288"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}query<\/code>\u00a0string syntax uses the following rules:<\/p>\n\n
:<\/code>\u00a0character is the equality operator. Other operators include\u00a0<<\/code>\u00a0(greater than) and\u00a0><\/code>\u00a0(less than), the minus sign\u00a0-<\/code>\u00a0(negation), and the wildcard (*<\/code>) character. See\u00a0Search operators<\/a>\u00a0in Zendesk help<\/p>\n<\/li>\n""<\/code>) are used for search phrases. The search only returns records that contain an exact match of the phrase.<\/p>\n<\/li>\ntype<\/code>\u00a0property returns records of the specified resource type. Possible values include\u00a0ticket<\/code>,\u00a0user<\/code>,\u00a0organization<\/code>, and\u00a0group<\/code>. See\u00a0Using the ’type’ keyword<\/a>\u00a0in Zendesk help<\/p>\n<\/li>\nstatus<\/code>\u00a0property returns tickets assigned to a specified ticket status. Other supported properties vary based on the record type. See the following reference guides in Zendesk help:<\/p>\n\n
\nURL encoding parameter values<\/h3>\n
query<\/code>\u00a0parameter. URL parameters are also called query parameters or query strings.<\/p>\nquery<\/code>\u00a0value of\u00a0type:ticket status:open<\/code>, the\u00a0:<\/code>\u00a0and space characters must be URL encoded as follows:<\/p>\n...\/api\/v2\/search.json?query=type%3Aticket+status%3Aopen<\/code><\/p>\nK\u00e4lla<\/strong>: Zendesk<\/a> |<\/pre>\n
\nSorting search results<\/h2>\n
\n
order_by:<em class="ph i">field<\/em><\/code><\/li>\nsort:asc<\/code>\u00a0or\u00a0sort:desc<\/code><\/li>\n<\/ul>\n<\/div>\n\n
created<\/code><\/li>\ncommented<\/code><\/li>\npriority<\/code><\/li>\nstatus<\/code><\/li>\nticket_type<\/code><\/li>\n<\/ul>\n<\/div>\norder_by<\/code>\u00a0and\u00a0sort<\/code>\u00a0keywords is equivalent to using the API parameters\u00a0sort_by<\/code>\u00a0and\u00a0sort_order<\/code>.<\/p>\n
\nUsing the ’type’ keyword<\/h2>\n
<em class="ph i">type<\/em><\/code>\u00a0keyword. It is used to explicitly declare that you want to search for one of the following types:<\/p>\n\n
type<\/code>\u00a0keyword means that you are explicitly searching on the type you specify. For example, you can search for all the users that belong to the customer’s organization using this search statement:<\/p>\ntype:user organization:customers<\/code><\/pre>\n<\/div>\norganization:customers<\/code>\u00a0you would also get all the tickets that have requesters who belong to this organization. This is because searches that do not explicitly specify type return results for all types, including tickets (and organization is a ticket property).<\/p>\ntype:user<\/code>, your search returns all users that belong to the Customers organization. So, you’re narrowing your search to the user type and excluding tickets.<\/p>\ntype:organization tags:premium<\/code><\/pre>\n<\/div>\n<\/div>\n<\/div>\nUsing the ’user’ keyword<\/h2>\n
user<\/code>\u00a0keyword:<\/p>\nuser:amy<\/pre>\n
type:user<\/code>\u00a0keyword:<\/p>\ntype:user amy<\/pre>\n<\/div>\n
user<\/code>keyword and how it’s different from the\u00a0type:user<\/code>\u00a0keyword, see the section about\u00a0The user and type keywords<\/a>\u00a0in\u00a0Searching users, groups, and organizations<\/em>.<\/p>\nK\u00e4lla<\/strong>: Zendesk search reference<\/a> |<\/pre>\n<\/div>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"