Demystifying iControl REST Part 4: Working with JSON Data

iControl REST. It’s iControl SOAP’s baby, brother, introduced back in TMOS version 11.4 as an early access feature but released fully in version 11.5. Several articles on basic usage have been wri...
Published Nov 10, 2015
Version 1.0
devops
iControlREST
python
series-demystifying-icontrol-rest
Adam_Burnett_18's avatar
Adam_Burnett_18
Icon for Nimbostratus rankNimbostratus
Nov 18, 2015
One thing I find particularly mystifying about the iControl REST API is the hodgepodge of data type representations. For example the boolean allowNat on a pool is "yes"/"no" where the boolean manual-resume on a monitor is "enabled"/"disabled". The monitors array on a pool is an "and" delimited string. How can we as the community push for a more "standards" based API? Is there a doc describing the API entities and allowable values for each?