add year and name to license
add license
create rough outline of openapi 3.1.0 documentation of API
Many cities, towns, and counties in the United States use Municode software to publish their codes of ordinances on the web. Municode presents ordinance content in a single-page app, and does not advertise any type of machine-readable API for accessing this content. This project is an attempt to reverse engineer the API Municode uses behind their SPA. I hope to make it possible for policy researchers, NLP experts, and developers of accessible clients to programmatically access the rules that govern our lives.
All Municode API endpoints can be accessed at https://api.municode.com
.
GET /codesToc/children
Get the children of a node in the document tree.
GET /CodesContent
Access the content of the current node in the document tree, as well as that of all child nodes.
GET /search
Search MuniDocs for a word or phrase.
GET /Clients/stateAbbr
Get a list of Municode clients in a particular US state.
GET /States/abbr
Get information about a US state based on its abbreviation.
GET /Clients/name
Get general information about a client based on its name and state.
GET /ClientContent/<clientId>
Get all Municode products a client has subscribed to, and what features are enabled for those products.
GET /Products/name
Get information on a particular product a client subscribes to.
GET /Jobs/latest/<jobId>
Get information about a particular job. I am guessing that a Job is a service supplied by Municode according to a contract with a particular government and over a certain period of time.