We've added Custom Field data to the 'list' equipment items endpoint for our Equipment Management API.
As this increases the amount of data delivered, and speed, we've made it an opt-in flag include_custom_fields=true parameter.
To use it, just add the parameter to the /v2/team/equipment endpoint. e.g. GET {server}/v2/team/equipment?include_custom_fields=true (see docs)
You can add multiple parameters to filter data on this endpoint, e.g. GET {server}/v2/team/equipment?location_id={id}&include_custom_fields=true.
The data you'll get back is something like this for each field for each item:
{
"id": //id of the custom field,
"entity_id": //id of the equipment item,
"secure": //bool if the field is marked secure,
"type": //type of custom field e.g. date,
"label": //title of the custom field,
"value_string": //string version of the value,
"value": //raw version of the value, e.g. id of multichoice,
"postfix": //symbol for after the value e.g. a unit,
"hint": //text hint for field,
"bundle": //field grouping,
"member_edit_own": //bool if the member can update this
"required": //bool for required field
"archived": //bool if archived or current
"ordering": //order in display list
"choices": //choices for multiple/single choice
},
