Views
Difference between revisions of "Open APIs"
Collaboration for an Open311 Standard
(→APIs) |
|||
| Line 6: | Line 6: | ||
* [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 | ||
| + | * * [http://lovecleanstreets.org/ Love Clean Streets] [http://api.mediaklik.com api] | ||
====City APIs==== | ====City APIs==== | ||
Revision as of 08:11, 12 October 2011
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
