Get Field Values
affinity_get_field_valuesGet all custom field values for any person, organization, opportunity, or list entry. Returns global and list-specific fields for data quality and analysis.
Instructions
Retrieve all field values for a specific entity (person, organization, opportunity, or list entry).
This is a V1 API endpoint - field values GET is NOT available in V2.
Returns complete custom field data for an entity including:
Global fields (account-wide custom fields)
List-specific fields (pipeline stages, deal amounts, etc.)
Field metadata (types, creation/update timestamps)
Use Cases:
Get all custom fields for a company: "What data is populated for this company?"
Inspect deal pipeline data: "Show me all fields for this list entry"
Data quality assessment: "Which companies are missing funding amount?"
Field comparison: "Compare field data between two opportunities"
Important: Exactly ONE Entity Parameter Required The API enforces that you must specify exactly one of:
person_id: Get field values for a person
organization_id: Get field values for an organization/company
opportunity_id: Get field values for an opportunity
list_entry_id: Get field values for a specific list entry
Providing zero parameters or multiple parameters will result in a 422 error.
Field Types: Field values include a value_type that indicates the data type:
0 = Person (references person ID)
1 = Organization (references organization ID)
2 = Dropdown (single-select text)
3 = Number (numeric value)
4 = Date (ISO timestamp)
5 = Location (city, state, country object)
6 = Text (free-form text)
7 = Ranked Dropdown (pipeline stages with id, text, rank, color)
8 = Formula (computed value)
9 = Interaction (email/meeting reference)
Global vs List-Specific Fields:
list_entry_id = null: Global field (applies across all lists)
list_entry_id = number: List-specific field (only for that list entry)
Field Name Resolution: Field values only contain field_id. To get field names:
Call GET /fields or GET /fields?list_id={id}
Map field_id to field name
Use the mapping to display human-readable field names
Parameters: Choose exactly ONE:
person_id: Person identifier (number)
organization_id: Organization/Company identifier (number)
opportunity_id: Opportunity identifier (number)
list_entry_id: List entry identifier (number)
Returns (JSON): { "fieldValues": [ { "id": number, // Field value ID "field_id": number, // Field definition ID (resolve with GET /fields) "entity_id": number, // Entity this value belongs to "entity_type": number, // 0=person, 1=organization, 2=opportunity "list_entry_id": number | null, // null=global, number=list-specific "value": any, // The actual value (type varies) "value_type": number, // 0-9 (see types above) "value_type_name": string, // Human-readable type name "created_at": string, // ISO timestamp "updated_at": string | null // ISO timestamp or null } ], "count": number, "entity_type": string, // "Person", "Organization", "Opportunity" "summary": string }
Example Use Cases:
Get company custom fields: { "organization_id": 303073231 } Returns: Description, Tech tags, LinkedIn URL, Location, Employee count, etc.
Get deal pipeline fields: { "list_entry_id": 227497865 } Returns: Status (Ranked Dropdown), Owners, Raise Amount, Stage, Female Founders, etc.
Get person fields: { "person_id": 250862100 } Returns: Source of Introduction, custom contact fields, etc.
Error Handling:
422: Must specify exactly one entity parameter
422: Invalid entity ID (entity does not exist)
Empty array: Entity exists but has no field values
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| person_id | No | Person ID - Get field values for this person (exactly one entity ID required) | |
| organization_id | No | Organization/Company ID - Get field values for this organization (exactly one entity ID required) | |
| opportunity_id | No | Opportunity ID - Get field values for this opportunity (exactly one entity ID required) | |
| list_entry_id | No | List Entry ID - Get field values for this list entry, including list-specific fields (exactly one entity ID required) | |
| responseFormat | No | Output format: "json" for structured data or "markdown" for human-readable. Default: "json" |