There is currently no consistency when toaster's API represents a layer object in JSON. The properties in the object you get back depend on which API end point you use, this makes it nearly impossible use the API. This also blocks further table porting to ToasterTables as some of the endpoints which would be used, already have their own custom JSON response that doesn't correspond to a compatible ToasterTable widget API JSON response.
API has been split up so it's now been possible to unify the object representation for layers which was the main issue here.
Verified obsolete.