Environment Changes

In the past, Wetpaint Injected has supported two environments: wapi.wetpaint.com, which is our production environment, and togo.wetpaint.com, which is our sandbox environment. Starting immediately, we will no longer be issuing keys for the togo.wetpaint.com environment. Going forward, all keys issued will be for the wapi.wetpaint.com environment.

In the meantime, we will continue to support the togo.wetpaint.com keys that have been issued until such time that we can transition existing users to wapi. While most references to the togo.wetpaint.com environment have been removed from the wetpaintinjected.com wiki, some sample code still references this environment. In the coming weeks we will be transitioning all of our sample code to reference wapi. This change is being made to roll out our Wetpaint Injected self-serve functionality, which allows anyone to sign up for a developer key. Also, this change will simplify our documentation as everything will point to wapi.wetpaint.com.

If you wish to have multiple Wetpaint Injected environments we suggest signing up for multiple developer keys. One of your developer keys can be used to host your sandbox environment, while the other can be used for production, etc.

API Changes

Two Wetpaint Injected APIs are changing. The documentation on the Wetpaint Injected wiki has been modified to reflect the changes. The changes are:

Load Bootstrap
When loading the client application bootstrap, we now require that you provide your developer key:

<script src="http://wapi.wetpaint.com/JavaScriptService/getBootstrap.do?key=<your developer key>" type="text/javascript"></script>

For more information, please refer to the Injected integration guide.

FeedService
Production feeds are now accessible via the feed.wapi.wetpaint.com:

GET /FeedService/getRecentlyUpdatedCells.do?ns=<wiki namespace> -- and -- GET /FeedService/getMostActiveCells.do?ns=<wiki namespace>

For more information, please refer to the FeedService API documentation.