Kickserv APIv2 - Object Maps
This documention is neither written nor endorsed by Kickserv. It has not been reviewed by Kickserv for accuracy and the API is entirely unsupported. It may work, it may not.
You are responsible for anything that you do using the API and Kickserv can't undo it for you. Use at your own risk.
The API returns quite a bit of data and sometimes it's not immediately obvious what everything is. The maps below will help get you going. It's not uncommon for one object to be nested inside another, so for example
an 'item' object may be inside a 'job charge' object, which is inside a 'time entry' object, which is found inside a 'job' object. Not all fields have been deduced, as some only show up in certain situations, or may have
been deprecated.
There are times when information is truncated and only the essentials are returned. The documents below map the 'full size' object whenever possible, though smaller versions of them may appear from certain endpoints.