• Announcements

  • End-of-life for Opalstack API v0 and the WebFaction migration tool

On October 9 2021 we will be retiring the v0 API endpoint at https://my.opalstack.com/api/v0/.

If you're using Opalstack's API then please update your code to use the v1 endpoint https://my.opalstack.com/api/v1/.

The API v1 endpoint is documented at https://my.opalstack.com/api/v1/doc/.

The WebFaction migration tool (wfmigrate) uses the old v0 endpoint, so that tool will be retired as well. WebFaction is officially shut down so the tool no longer has any use.

If you have any questions or concerns then please email them to support @ opalstack.com and one of our team will get back to you.

sean That makes it a perfect location for the API documentation. (I think that's what Swagger does?) Just sayin'... 😁

P.S. Is there a good place to read about possible use cases for the Opalstack API? I don't think I need to use it for anything, but occasionally other people's use cases turn out to be surprisingly relevant to my own needs.

  • sean replied to this.

      Is there a good place to read about possible use cases for the Opalstack API?

      The most important use-case could be a hosting control panel for re-sellers.

      john-asl the swagger docs are at https://my.opalstack.com/api/v1/doc/ and https://my.opalstack.com/api/v1/redoc/.

      The general use case for the API is the automation of tasks that you would otherwise do manually in the dashboard. For example if you frequently create new Wordpress sites, then you could create a tool that does the following:

      1. Adds the domain.
      2. Creates the WP app.
      3. Creates a site to serve the app on its domain.
      4. Creates a mailbox and email address for the site.
        5 days later

        Hey @sean -- are there any major changes between v1 and the last iteration of v0?

        • sean replied to this.

          sean ok thanks.

          For what it's worth, I'm not sure that this part is very clear in the docs:

          sean All create/update endpoints now take lists of objects instead of individual objects

          On /app/create for example, the "Example Value" (and "Model") both look like an individual object to me? The "data" param also says object.

                Mastodon