From their site: Dabble lets you do a lot without ever having to write a line of code — from simple data modeling, to standard CRUD operations (creation, retrieval, update and deletion), importing and exporting data, searching, and back-linking, Dabble handles the common recurring data management tasks for you. Sometimes, though, you need your Dabble application to do something very specific to you or your users. You may have a custom algorithm you want to apply, or you might want to pass your data through a third-party web service. This is where the Dabble Plugin API comes in.
Dabble plugins allow Dabble applications to create new, derived fields by calling out to external HTTP-accessible applications. This solves the problem of safely enabling extension of a centrally-located hosted application, in that, while you’re writing code to extend and enhance the behavior of a Dabble application, your code never actually runs inside Dabble. You might even think of it as a plug out as opposed to a plug in.
The following is a list of historical changes that were made to this asset. Typically,
once an API is published on ProgrammableWeb.com, the data we keep about that asset gets updated over the course of its life. For example, the endpoint or home page of the documentation might change.
As a means of enforcing the integrity of our data, every time a non-trivial change is made to the data we keep about an asset,
we require the entry of some changelog text before that change can be saved. This way, we have a great audit trail of all
activity surrounding the asset. For each asset, the changelogs begins with the moment an asset is approved for publication on ProgrammableWeb.
If you spot an error in our data and believe that a record needs to be updated in some way,
the ProgrammableWeb team would very much like to hear from you at firstname.lastname@example.org