Views
Difference between revisions of "Open APIs"
Collaboration for an Open311 Standard
Piternoize (Talk | contribs) |
(Undo revision 1329 by Piternoize (talk)) |
||
| Line 4: | Line 4: | ||
* [http://www.fixmystreet.com/import FixMyStreet API] - live. Very basic POST interface. (write-only) | * [http://www.fixmystreet.com/import FixMyStreet API] - live. Very basic POST interface. (write-only) | ||
* [http://wiki.ushahidi.com/doku.php?id=ushahidi_api Ushahidi API] live | * [http://wiki.ushahidi.com/doku.php?id=ushahidi_api Ushahidi API] live | ||
| − | |||
* [http://geochathelp.com/doku.php?id=api:documentation GeoChat API] live | * [http://geochathelp.com/doku.php?id=api:documentation GeoChat API] live | ||
* [http://help.seeclickfix.com/faqs/api/ SeeClickFix proposed API] - draft | * [http://help.seeclickfix.com/faqs/api/ SeeClickFix proposed API] - draft | ||
Latest revision as of 20:13, 30 January 2012
There are several APIs in development. The City APIs are synthesizing best practices from each and coalescing into the international specification. Currently San Francisco is developing the most up to date implementation of the Open311 specification.
APIs
- FixMyStreet API - live. Very basic POST interface. (write-only)
- Ushahidi API live
- GeoChat API live
- SeeClickFix proposed API - draft
- * Love Clean Streets api
City APIs
- DC open311 API v1 - live (read/write)
- DC open311 API v2 - draft
- SF open311 API - in development (the SF Gov Open311 page currently points here)
API Design
- Open311.org API - Spec Draft & System Architecture Proposal
