Lists stored custom field values across contacts, one entry per contact-and-field pair, 20 per page by default. Each entry's contact property is the contact id, field is the custom field definition id, and value holds the stored text. Use filters[fieldid] to scope to one field, contacts[] to scope to contacts, or GET /contacts/{id}/fieldValues for a single contact's values. Values whose contact row no longer exists are excluded. Use only the query parameters documented here: unsupported filter and order fields are silently ignored, so the response looks filtered but is not; filters match exactly. Date and datetime values are returned in ISO 8601 in the API user's timezone. meta.total is the number of matching values, returned as a string; id_greater and id_less do not change it. For a user outside the Admin group calling the API directly, only values of fields available on one of the user's lists (or on all lists) are returned. Without orders, id_greater or id_less, the order is not defined. Values that are equal under orders[fieldid] or orders[val] also come back in no defined order; send orders[id] last to make it stable. To read a large set, page by id instead of by offset: a large offset gets slower with every page, while each id_greater page costs the same however far in.
{
"fieldValues": [
{
"contact": "5",
"field": "1",
"value": "Burger",
"cdate": "2018-09-29T12:03:11-06:00",
"udate": "2018-09-29T12:03:11-06:00",
"links": {
"owner": "https://:account.api-us1.com/api/3/fieldValues/1/owner",
"field": "https://:account.api-us1.com/api/3/fieldValues/1/field"
},
"id": "1",
"owner": "5"
},
{
"contact": "7",
"field": "2",
"value": "2018-05-10",
"cdate": "2018-04-24T12:04:46-06:00",
"udate": "2018-04-24T12:04:46-06:00",
"links": {
"owner": "https://:account.api-us1.com/api/3/fieldValues/2/owner",
"field": "https://:account.api-us1.com/api/3/fieldValues/2/field"
},
"id": "2",
"owner": "7"
}
],
"meta": {
"total": "2"
}
}