The custom fields your company has set up. Read this before working
with custom field values, so you know which fields exist and which
id to use for each one.
You only see your own company's custom fields, and only the ones that
are switched on and made available to the API.
Match on id, never on label. A label is the name shown on
screen and can be renamed at any time. More importantly, several
fields can share one label — that is normal, not a mistake in your
data, which is why each field also carries a key with its id on the
end, like email_697 and email_713. The numeric id is the only
value that is guaranteed to mean one field.
Where a field appears. placement tells you which screen a field
shows up on: loan for the loan file only, profile for the borrower
profile only, and loanAndProfile for fields that appear on each. A loanAndProfile
field holds two separate values — one stored against the loan and
one against the borrower. They are different records and can hold
different answers.
An empty list is a real answer. Your company may simply not have
set any custom fields up. You get a normal, empty list rather than an
error.
Order. Grouped by section in the order your sections are arranged,
then by the order the fields are arranged inside each section.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||

