I recently released an API for the current product versions of Snow Software products. This information is publicly available from Snow Software, but I’ve always found their current product version pages to be quite clunky and full of information that I don’t need at that specific time, i.e I just want to know the versions and not the changes at that specific moment, thus that’s where snwAPI came from.
This was originally created as a project that I didn’t imagine many people would use, so I just popped it on a subdomain of my website and was going to leave it there. Since it was released, it has had a lot more traffic than I expected so I have decided to move it to a dedicated domain and update things (documentation rather than API changes) a little bit.
So what is the actual plan? I’m glad you asked.
- Move from ext.laim.scot/snowapi to snwapi.com.
- Expand on the documentation.
- Branding change from ‘Snow Version API’ to ‘snwAPI’ to account for future projects.
I don’t have a set time frame for this at the moment, as it depends entirely on when I am free to make the changes and move the database over that it’s currently using, however I’m expecting this to be finished by the end of October 2020.
What do I need to know?
The current API URL will NOT be redirected. I decided to do this to prevent people from using the legacy URL, this might be a bit annoying for people that are using it but it’s not a massive change as the code and layout won’t change, it’s merely a URL change.
Just to reitterate, this change is being made now to account for future products as well as easier maintaining, without it having my name all over meaning it may be easier for companies, engineers or analysts to persuade their management to let them use it in an internal tool, etc.