Open311

Wiki

Collaboration for an Open311 Standard
Personal tools

Difference between revisions of "API"

Collaboration for an Open311 Standard

Jump to: navigation, search
(→‎Client Apps)
(→‎Client Apps)
Line 39: Line 39:
 
Client applications can send and/or view reports
 
Client applications can send and/or view reports
 
* [http://help.seeclickfix.com/kb/api/api-overview SeeClickFix]
 
* [http://help.seeclickfix.com/kb/api/api-overview SeeClickFix]
−
* [http://www.facebook.com/SF311?sk=app_128760367192739 Facebook App] (for San Francisco's Open311 API)
+
* [http://www.facebook.com/SF?sk=app_128760367192739 Facebook App] (for San Francisco's Open311 API)
  
 
====Test Suites====
 
====Test Suites====

Revision as of 17:09, 17 March 2011

Open311 APIs

GeoReport v2

Spec: GeoReport v2

Here is a proposal for doing specifying metadata about Open311 endpoints. It is expected that a version of this will be included in v2. Service Discovery

Servers

Servers receive and manage reports on behalf of a jurisdiction.

Note that the URLs require a method and jurisdiction_id at the end, the root URL is not intended to be accessed directly.

Name Status API Key Dev API Production API
San Francisco Development Ready Request Key Dev URL Production URL
Washington D.C. Development Ready - - Production URL

Server Software

Server applications can receive and manage reports

Client Apps

Client applications can send and/or view reports

Test Suites

Test suites are used to verify that a server is compliant with the specification.

Client Libraries (API Wrappers)

Client libraries make it easier to build client applications that work with the spec.

GeoReport v1

Spec: GeoReport v1

Servers (can receive reports)

Name Status API Key Dev API Production API
City of San Francisco Production Ready Request Key Dev URL Production URL

Clients (can send and view reports)

Client Libraries (API Wrappers)

Inactive APIs