Use this query to list multiple issues.
|Valid Data Formats||xml, json, kml, rss (geoRSS)|
|Permissions||read only. API key not required.|
Area in the form of one area type below.
|watcher_token||Random string given after creating a watch area.||All area within the associated polygon.|
||Area will be the bounding box of a 650px X 650px map at the zoom level given surrounding the geocoded location. If no zoom is give, zoom will be determined from geocoding accuracy (i.e. street, city, or country level).|
|lat, lng, and zoom||
||Area will be the bounding box of a 650px X 650px google map at the zoom level given surrounding the lat/lng location given.|
|lat_min, lat_max, lng_min, lng_max||
||Limit issues to bounding box defined by lat min/max and lng min/max.|
- status[Open] - Set equal to "true" to see open issues. If status is not set the API returns Open, Closed, and Acknowledged issues.
- status[Closed] - Set equal to "true" to see closed issues. If status is not set the API returns Open, Closed, and Acknowledged issues.
- status[Acknowledged] - Set equal to "true" to see acknowledged issues. If status is not set the API returns Open, Closed, and Acknowledged issues.
- status[Archived] - Set equal to "true" to see archived issues. If status is not set the API returns Open, Closed, and Acknowledged issues.
- start – The number of hours ago the oldest issue can be. Partial hours can be in decimal format, for example 0.25 shows reports in the last 15min.
- end – The number of hours ago the youngest issue can be.
- num_results - The maximum number of results to return (default 10, maximum 1000).
- page – If the number of results exceeds num_results, page can increment the range.
- search – A query string to limit the results by.
- sort – A parameter to sort the results
by. Possible values include: issues.updated_at - Date last
Issues.created_at - Date Created
Issues.rating - Issue Rating
Issues.hot - Issue Hotness
- direction – Sort direction. Possible
values include: ASC - Ascending
DESC - Descending.
- request_tags – Limit results to issues with service request tags. Service request tags are automatically added to issues when issues are reported to a specific service request. Multiple request tags can be found using the form "request_type_[request_type_id],request_type_[request_type_id],request_type_[request_type_id]".
This query says show me all issues within “New Haven, CT” from a zoom level of 10. Limit the results by issues updated in the last 24 hours and only the last 5 created.
Data is returned in chunks of num_results. You can increment the page parameter to get the next group of results. If page exceeds the total number of pages the result will be an empty array. For example, say you want 10,000 results of graffiti. You can make 10 requests with page from 1 to 10 and num_results = 1000.
SeeClickFix data sources, including XML, RSS, KML and JSON, are licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 United States License. Attribution should be to seeclickfix.com.
Persons or organizations wishing to reuse large portions (ie., more than occasional queries ) of data are required to contact us first at email@example.com. We are very interested in working with researchers and/or agencies to ensure that this data is put to good use!
- Help! I have no idea where to put my issue on the map!
- I'm trying to report an issue, but when I click on its address the red marker jumps somewhere else.
- When I type the name of the town I want into the search bar, I get taken somewhere else.
- I want to change something about an issue after I reported it.
- Closing an Issue
- View all (1 more)