v1
latestOpenAPI 3.1.02026-07-261770816.7 KBList custom fields
Custom fields are the org-defined dictionary of structured data your organization layers onto core resources — jobs, offers, openings, candidates, applications, and users. Each row defines one field: its field_type selects the parent resource it attaches to, and its value_type selects the data type and editor (text, number, currency, single/multi-select, date, user, attachment, etc.). Replaces the V1 path-scoped endpoints /v1/custom_fields/{field_type} — filter by field_type as a query parameter instead. For select-type fields, options live on the sibling resource /v3/custom_field_options; office/department visibility lives on /v3/custom_field_offices and /v3/custom_field_departments.
Query parameters
Cursor link for pagination from previous page response header. Do not use any other parameters when using this.
Number of results per page
Comma separated list
Comma separated list of fields to return
Filter by the resource the field attaches to (e.g. job, offer, candidate, application, opening, user_attribute). Replaces the V1 path segment /v1/custom_fields/{field_type}.
Filter by archival status. Defaults to returning both active and archived; set true for live fields only, false for archived only.
Filter to fields whose human-readable name exactly matches this value (case-insensitive).
Filter to the field with this name_key (the stable lowercase identifier used when setting values on parent resources). Prefer this over name for integrations — name_key is stable across rename.
Response
Successful