Octopus Deploy 2.0 API changes - RFC
Blog post from Octopus Deploy
Octopus Deploy's RESTful HTTP API, initially designed to support the command line tool Octo.exe, is set to become a primary focus in the upcoming Octopus Deploy 2.0 release, elevating it from a secondary role. Previously, the API was largely read-only, except for certain functions like machines, releases, and deployments, and it lagged behind the UI in terms of feature updates. The new version aims to integrate the API as a core component of the UI, facilitating faster and more fluid interactions even on large installations, by having the UI make asynchronous API requests instead of direct posts to MVC controllers. Additionally, the API will be thoroughly documented to support developers building on top of it, with a GitHub project created to invite community feedback and contributions to the documentation.