(→Servers) |
|||
| Line 8: | Line 8: | ||
===Servers=== | ===Servers=== | ||
| − | Servers receive and manage reports on behalf of a jurisdiction | + | 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.'' | ||
{| class="wikitable sortable" | {| class="wikitable sortable" | ||
! Name | ! Name | ||
| Line 24: | Line 26: | ||
| '''Washington D.C.''' | | '''Washington D.C.''' | ||
| ''Development Ready'' | | ''Development Ready'' | ||
| − | | | + | | - |
| − | | | + | | - |
| − | | [http:// | + | | [http://311.dc.gov/cwi/Open311/v2/ Production URL] |
|} | |} | ||
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 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 applications can receive and manage reports
Client applications can send and view reports
Test suites are used to verify that a server is compliant with the specification.
Client libraries make it easier to build client applications that work with the spec.
| Name | Status | API Key | Dev API | Production API |
|---|---|---|---|---|
| City of San Francisco | Production Ready | Request Key | Dev URL | Production URL |