The Inquiry/Information API is meant to be accessed to retrieve non-GeoReport-related content. This can be used for information which is typically provided to callers of a 311 system as an answer to their question. It supports three fundamental capabilities: services, facilities, and a "311 today" (RSS) feed.
Version 2 is meant to provide a more generic version of the Inquiry/Information API with extended features.
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 receive and manage service requests on behalf of a jurisdiction. A comprehensive list is being maintained on the GeoReport v2 Servers page
Open source developer resources for the GeoReport v2 specification.
Server applications provide an API endpoint and can receive and manage reports.
Software that interacts with an Open311 server by connecting to an API.
See also open source libraries for Visualizations
Client libraries make it easier to build client applications that work with the spec.
Test suites are used to verify that a server is compliant with the specification.
See also GeoReport v2 Support for products and services.
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||city_id||Dev API||Production API|
|San Francisco||Deprecated August 2013||[Deprecated]||sfgov.org||[N/A Dev URL]||[N/A Production URL]|
|Miami-Dade County||Development Ready||Request Key||miamidade.gov||Beta URL||-|