Open311 APIs

GeoReport v2

Spec: GeoReport v2

Service Discovery

GeoReport v2 and following versions are meant to be accessed via the Service Discovery mechanism to identify the status and version number for available endpoints in each jurisdiction. The service discovery mechanism is a requirement of the specification, but is meant to be independent and persistant beyond the GeoReport v2 version of the spec.

Please view the Service Discovery specification.

Servers

Servers receive and manage reports on behalf of a jurisdiction.

Servers receive and manage service requests on behalf of a jurisdiction. A comprehensive list is being maintained on the GeoReport v2 Servers page

Server Software

Server applications can receive and manage reports

• http://svn.ashlock.us/public/georeport-v2-api-php/ (in development)
• http://svn.ashlock.us/public/georeport_ushahidi/v2/ - Ushahidi integration, see demo (in development)

Client Apps

Client applications can send and/or view reports

• SeeClickFix
• HeyGov

Test Suites

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

• http://github.com/open311/open311-validator (in development)

Client Libraries (API Wrappers)

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

• Ruby Gem by Dan Melton et al
• Node.js by Mark Headd
• C Sharp by Mark Headd

GeoReport v1

Spec: GeoReport v1

Servers (can receive reports)

Clients (can send and view reports)

• SeeClickFix
• CitySourced
• TweetMy311
• Facebook App (for San Francisco's Open311 API)

Client Libraries (API Wrappers)

• PHP Library by Mark Head

Inactive APIs

• DC Open 311 v1