Thanks to your feed-back, we have spent the past month improving APISpark with more stability and new features. Find below and overview of the changes available in production!
We are also extending access to the public beta to even more users in the waiting list.
Faster API deployment
We have significantly reduced the API deployment time by moving the generation of downloadable elements (client SDKs and offline documentation) to a separate action.
See the new “Generate downloads” action in the actions menu below.
In addition, we fixed a regression with the iOS client SDK that what causing it to include unecessary and large files. The result is a faster generation of downloads as well.
Flexible life cycle
Based on your feed-back (special thanks to Rob Bontekoe), we realized that the difference between Deploy and Publish actions isn’t clear.
To summarize, Publish is an action that moves draft APIs or Data Stores forward in their life cycle. Once published, the Deprecate action is then available and finally Archive.
On the contrary, the Deploy action is always available and doesn’t change the status of a cell (API or Data Store), it only regenerates and updates it on the runtime platform.
Now, when an API is published, it becomes impossible to change its contract in order to prevent breaking users’ applications. If changes need to be made, it is however possible to create a new version of the API in parallel which will be in Draft mode.
However, while users are discovering APISpark, they are tempted to publish an API and then changing their mind before inviting external API users. For this case, we added a new “Revert to draft” action to the drop down menu as illustrated above.
Custom domain names
Each API created on APISpark is given a subdomain such as mycompany.apispark.net which is an easy way to get started. However, more advanced API projects will prefer to use their own domain name such as api.mycompany.com.
We are pleased to announce that custom domains are now available on APISpark. They can be added to an API by going to the “All versions” level in the version combo box, then using the Domains section as illustrated below.
Please note that you need to add a new DNS record to your DNS registry in order to properly route the traffic to your API hosted by APISpark.
Once enabled, you can return to any API version and create a new endpoint, selecting the new domain name. Redeploy your API and you are good to go!
Finally, we fixed several issues:
- Fixed conflict when deploying an API and a Store with the same name
- API deletion is not complete, including the release of the domain name
- Completed the offline HTML doc generated, including a light CSS
- Fixed regression when generating the offline PDF doc
- Improved sign in by giving feed-back to unauthorized users
- Improved sign out by redirecting to the APISpark.com home page
- Security rights and action conditions weren’t displayed properly in UI
- URI path variables are now generated by the “Add resources” wizard
- Merged Info, Copyright & User Agreement sections
- Entity, Resource & Representation names restricted to a-z, 0-9 and ‘_’
Updated road map
Based on our progress and the feed-back received, we have refined our road map for the next few months, with the release of version 1.0 expected for June 2013.
Select the road map picture above for additional details.
If you want to see how creating, hosting and using web APIs looks like with APISpark, we recommend our first tutorial.