altRequests results in an alternative formatValues: atom, rss, json, json-in-scriptDefault: atomExample: ...&alt=rsscallbackCauses the specified JavaScript function name to be executed when the data from Google Base is loadedDefault: NoneNotes: Only used when alt=json-in-scriptExample: ...&alt=json-in-script&callback=yourProcessResultsFuncorderbyDefine the ranking order for sorting queriesValues: relevancy, modification_time, name(type):value, []Default: relevancyNotes: The Ranking Language reference explains what you can do with this language and defines the language syntax.Example: ...&orderby=price(float USD)crowdbyLimit repetitive results by placing a cap on similar itemsValues: attribute, url, customerid, content, [expression]Default: 1Notes:The syntax is a comma-separated list of crowding criteria and maxvalue pairs: (i.e. &crowdby=crowding:maxvalue,crowding:maxvalue,...). The totalResults for the feed will still reflect the number of results that would have been available had crowding not been imposed.Crowding criteria, read moreExample: * Show each item's color a max of 2 times: ...&crowdby=color(text):2 * Show only 3 items originating from each url: ...&crowdby=url:3

sortorderQuery results are returned in increasing or decreasing order.Values: ascending, descendingDefault: descendingNotes: If sortorder is specified but orderby is not, the results will be sorted by relevancy in the specified order.Example: ...&orderby=price(float USD)&sortorder=ascendingrefineRefines the query resultsValues: true, falseDefault: falseNotes:The purpose of this mechanism is to restrict search results to items that reuse a certain number of attributes we consider to be essential for a given item type. This may improve the quality of certain search results, especially for queries that have many matching items.On the other hand, setting refine=true might lead to items getting dropped that actually match the specified query. This is, in particular, bad for the customer-specific items feed, because it can give the impression that some attributes are missing, when in fact they simply do not meet the undocumented quality assumptions that this parameter introduces.Because of this, refine=false by default. It should be enabled to improve quality of broad queries.Example:[item type: recipes][label:asian]gets rewritten to:[item type: recipes][cooking time][main ingredient][label:asian]