| Name | Type | Description | Notes |
|---|---|---|---|
| first_name | string | First name of the contact | [optional] |
| last_name | string | Last name of the contact | [optional] |
| string | Email address of the contact (required and must be unique within team). Validation: - Must be a valid email format - Must be unique within the team - Cannot be empty or null | ||
| company | string | Company name of the contact | [optional] |
| custom_fields | array<string,string> | Custom fields as key-value pairs. Keys should use `field_` prefix. Processing: - Keys are case-sensitive - Values are stored as strings Examples: - `"field_MnuqBAG2NPLm7PZMWbjQxt": "Engineering"` → stored as `department: Engineering` | [optional] |
| lists | string[] | Array of list identifiers to associate with the contact. Identifiers should use `list_` prefix. Processing: - Invalid list IDs will send our 400 error - Duplicates will be removed Examples: - `"list_OcuxJHdiAvujmwQVJfd3ss"` → valid prefixed format | [optional] |
| tags | string[] | Array of tag identifiers to associate with the contact. Identifiers should use `tag_` prefix. Processing: - Invalid tag IDs will be ignored - Duplicates will be removed Examples: - `"tag_UhsDkjL772Qbj5lWtT62VK"` → valid prefixed format | [optional] |
| last_tracked_ip | string | Last tracked IP address of the contact for analytics purposes. Usage: - Used for geographic analytics - Helps with spam detection - Optional field | [optional] |