Changing the checkpoints for certain customers in GUI

Yes, the API is the way to go along with properties to guide the API for how to adjust settings.  We also use the API for websites to detect when SSL monitoring is “off” (e.g., missing or non-standard thresholds), but really it would be better to define a property set per client that the API script uses to update that subtree.  Unfortunately, website “templates” are entirely global so cannot be adjusted per client and there are no tokens available for step descriptions -- those have been problems forever and I don’t see LM making any plans to fix them at this point.