API Documentation Update/Backwards Compatibility

[mguidon]

Not all endpoints are documented and accessible via api.server/dev/doc. It seems that endpoints listed there have a higher chance to remain backwards compatible.

Sim4life currently uses those endpoints:

• GET api/v0/
• GET api/v0/me
• POST web-api/v0/auth/api-keys
• DELETE web-api/v0/auth/api-keys
• POST web-api/v0/auth/login
• GET api/v0/solvers/{solver_key}/releases/{version}
• POST api/v0/solvers/{solver_key}/releases/{version}/jobs
• POST api/v0/solvers/{solver_key}/releases/{version}/jobs/{job_id}:start
• GET api/v0/solvers/{solver_key}/releases/{version}/jobs/{job_id}/metadata
• PATCH api/v0/solvers/{solver_key}/releases/{version}/jobs/{job_id}/metadata
• GET api/v0/solvers/{solver_key}/releases/{version}/jobs/page?
• GET api/v0/solvers/{solver_key}/releases/{version}/jobs/{log_id}/logstream
• GET api/v0/solvers/{solver_key}/releases/{version}/pricing_plan
• GET api/v0/wallets/{wallet_id}
• POST api/v0/solvers/{solver_key}/releases/{version}/jobs/{job_id}:inspect
• GET api/v0/solvers/{solver_key}/releases/{version}/jobs/{job_id}/output/logfile
• POST api/v0/solvers/{solver_key}/releases/{version}/jobs/{job_id}:stop
• GET api/v0/solvers/{solver_key}/releases/{version}/jobs/{job_id}/outputs
• DELETE api/v0/solvers/{solver_key}/releases/{version}/jobs/{job_id}
• GET api/v0/files/{file_id}/content
• POST api/v0/files/content
• POST api/v0/files/{file_id}:complete
• POST api/v0/files/{file_id}:abort
• GET api/v0/files:search