Views
Difference between revisions of "API"
Collaboration for an Open311 Standard
(→GeoReport v1) |
|||
| Line 11: | Line 11: | ||
===Spec: [[GeoReport v1]]=== | ===Spec: [[GeoReport v1]]=== | ||
| − | === | + | ===Servers (can receive reports)=== |
| − | + | ====='''San Francisco'''===== | |
| + | * Status: ''Production ready'' | ||
| + | * [http://apps.sfgov.org/Open311API/?page_id=486 Request API Key] | ||
| + | * API URL: [https://open311.sfgov.org/dev/V1 Dev Endpoint], [https://open311.sfgov.org/V1 Production Endpoint] | ||
| − | === | + | ===Clients (can send and view reports)=== |
| − | * SeeClickFix | + | * [http://seeclickfix.blogspot.com/2010/05/seeclickfix-integrates-data-with-san.html SeeClickFix] |
| − | * CitySourced | + | * [http://blog.citysourced.com/index.php/54/citysourced-integrates-san-franciscos-open-311-system/ CitySourced] |
| − | * | + | * [http://tweetmy311.org/ TweetMy311] |
=Inactive APIs= | =Inactive APIs= | ||
* [http://octolabs.pbworks.com/Open-311-API DC Open 311 v1] | * [http://octolabs.pbworks.com/Open-311-API DC Open 311 v1] | ||
Revision as of 10:54, 14 May 2010
Contents
Open311 APIs
GeoReport v2
Spec: GeoReport v2
Input (can receive reports)
- San Francisco Request API Key
- Washington D.C. Status: Development Ready. Request API Key
GeoReport v1
Spec: GeoReport v1
Servers (can receive reports)
San Francisco
- Status: Production ready
- Request API Key
- API URL: Dev Endpoint, Production Endpoint
