While some sort values make inference of the expected min/max values less than ambiguous, others do not.
Pending formal documentation, I hope this can serve as an informal reference.
Aggregated sort values and corresponding min/max datatype
activity:unix timestamp- last activity date range (includes any activity?)creation:unix timestamp- creation date rangeadded:unix timestamp- added date rangereputation:integer- reputation count rangeviews:integer- view count rangevotes:integer- vote count rangepopular:integer- tag count rangename:string- case insensitive range. e.g. to find exact match for users withdisplay_name'joey' you can sendmin=joey&max=joeyfeatured:unix timestamp- last activity date range (includes any activity?)hot:unix timestamp- last activity date range (includes any activity?)month:unix timestamp- last activity date range (includes any activity?)week:unix timestamp- last activity date range (includes any activity?)
Special Sorts:
These sorts return the questions that are displayed on the front page of the site under the tab of the same name. min/max will further limit those sets to questions with a last_activity date that falls within that range.
featured: Questions with an active bountyhot: Questions with the most interest/activity in the last few dayweek: Questions with the most interest/activity in the last weekmonth: Questions with the most interest/activity in the last month
You can follow the comment trail on min/max parameters are incorrectly documented as date - confusion and crippled libraries ensue for some more info that may be edifying.
dateand featured is also adatei believe.