IMPORTANT INFORMATION TO REMEMBER ABOUT CALIBER IMPLEMENTATIONS:
They have a self-hosted vs. Caliber-hosted situation similar to how TOPS Pro was. In most cases they will have their Caliber data hosted by Caliber. WE NEED TO BE SURE TO ASK. If they are self-hosted we need to observe the following difference in implementation of credentials:
Other caliber API generates the Authorization key with the combination of userid and password. But this Caliber client generates with the combination of APICode(which we don’t maintain in DB), userid and pwd. It is mentioned in the Spec doc. So I updated the DB values of siteurl and userid to this.

If we do not spice in that additional “associationready” into the userid in SQL it will produce a 401 (access denied) error
so “associationready:userid” into the userid field