Update API docs

[wpears]

Currently the generated API docs include "api" in the path, eg,
http://<servername>/api/isValidMSA/:activityYear/:msa

However, no Kraken controller exists for /api and as such all the example routes are incorrect (dropping the /api part makes them valid).

Perhaps this was included in case the api was sitting behind a reverse proxy which required additional path components to reach the api but then only passed the remaining path fragments, eg, curl server/some/path/isValidMSA/12345 but the app only sees the /isValidMSA/12345 part.

Either way, I'd say remove /api from the docs and perhaps include a note about how to deal with the api not accepting requests at the root path of the server.

[LinuxBozo]

This is definitely a shortcoming in the documentation. To get around CORS issues, it is best to run the API bits behind a proxy within the same FQDN that the frontend (hmda-pilot) is running. This ensures that everything is requested from the same FQDN, thus eliminating issues with CORS.