Returns the team-level custom field definitions applicable to transactions. Use the returned ids when populating LeadTransaction.customFields on create / update.
Scope: the caller’s team.
curl --request GET \
--url https://api.lofty.com/v1.0/transaction/customfields \
--header 'Authorization: <authorization>'[
{
"id": 1001,
"name": "Closing Agent",
"type": "Single-Select",
"params": "[{\"label\":\"Option A\",\"value\":\"1\"},{\"label\":\"Option B\",\"value\":\"2\"}]"
}
]Documentation Index
Fetch the complete documentation index at: https://developer.lofty.com/llms.txt
Use this file to discover all available pages before exploring further.
Bearer [access_token]
List of custom field definitions (may be empty).
Custom field id.
1001
Custom field display name.
"Closing Agent"
Custom field data type. Note the mixed casing: Single-Select and Multi-Select are emitted with hyphens and mixed case, while the other values are the upper-case enum names.
DATE, TEXT, NUMBER, PERCENTAGE, Single-Select, Multi-Select, CURRENCY, HTML "Single-Select"
For Single-Select and Multi-Select types, a JSON string encoding the option list, e.g. "[{"label":"Option A","value":"1"},{"label":"Option B","value":"2"}]". Empty or null for non-select types.
"[{\"label\":\"Option A\",\"value\":\"1\"},{\"label\":\"Option B\",\"value\":\"2\"}]"
curl --request GET \
--url https://api.lofty.com/v1.0/transaction/customfields \
--header 'Authorization: <authorization>'[
{
"id": 1001,
"name": "Closing Agent",
"type": "Single-Select",
"params": "[{\"label\":\"Option A\",\"value\":\"1\"},{\"label\":\"Option B\",\"value\":\"2\"}]"
}
]