Views
Difference between revisions of "Open APIs"
Collaboration for an Open311 Standard
| Line 7: | Line 7: | ||
* [http://wiki.open311.org/San_Francisco#SF_Open_311_API SF open311 API] - in development ''(the [http://apps.sfgov.org/Open311API/?page_id=382 SF Gov Open311 page] currently points here)'' | * [http://wiki.open311.org/San_Francisco#SF_Open_311_API SF open311 API] - in development ''(the [http://apps.sfgov.org/Open311API/?page_id=382 SF Gov Open311 page] currently points here)'' | ||
* [http://wiki.open311.org/Open311.org_Draft_Spec#System_Architecture Open311.org API] - Spec Draft & System Architecture Proposal | * [http://wiki.open311.org/Open311.org_Draft_Spec#System_Architecture Open311.org API] - Spec Draft & System Architecture Proposal | ||
| + | * [http://wiki.ushahidi.com/doku.php?id=ushahidi_api Ushahidi API] live | ||
Revision as of 00:19, 18 January 2010
There are several APIs we know of, all in development:
- FixMyStreet API - live. Very basic POST interface. (write-only)
- DC open311 API v1 - live (read/write)
- DC open311 API v2 - draft
- SeeClickFix proposed API - draft
- SF open311 API - in development (the SF Gov Open311 page currently points here)
- Open311.org API - Spec Draft & System Architecture Proposal
- Ushahidi API live
