Odoo 19.0 Community · Persistent

hr.applicant: fields, relations and API

The hr.applicant model ("Applicant") is a persistent model declared by the Recruitment module, then extended by 4 other modules. It exposes 109 fields, 69 of them declared directly on the model; 11 fields from other models point to it. Below you will find every field with its technical name, type, label and relations, followed by an Odoo 19 JSON-2 API call.

View source code Search another model

Model identity

Technical name: hr.applicant
Label: Applicant
Type: Persistent (models.Model)
SQL table: hr_applicant
Origin module: Recruitment (hr_recruitment)
Extended by: hr_recruitment_skills, hr_recruitment_sms, hr_recruitment_survey, website_hr_recruitment
Default order (_order): priority desc, sequence, id desc
Display field (_rec_name): partner_name
Inherits from (mixins): mail.thread.cc mail.thread.main.attachment mail.thread.blacklist mail.thread.phone mail.activity.mixin utm.mixin mail.tracking.duration.mixin

Model fields

69 own fields, 35 inherited from mixins and 5 automatic ORM fields. Click a name to get a direct link to that field.

Hide inherited fields

109 of 109 fields shown

Technical name	Label	Type	Details
active	Active If the active field is set to false, it will allow you to hide the case without removing it.	`boolean`
applicant_notes	Applicant Notes	`html`
applicant_properties	Properties	`properties`
applicant_skill_ids	Skills	`one2many` → hr.applicant.skill	inverse: `applicant_id` added by Recruitment - Skills Management (`hr_recruitment_skills`)
application_count	Application Count Applications with the same email or phone or mobile	`integer`	computed
application_status	Application Status	`selection`	computed Values: `ongoing` (Ongoing), `hired` (Hired), `refused` (Refused), `archived` (Archived)
attachment_ids	Attachments	`one2many` → ir.attachment	inverse: `res_id`
attachment_number	Number of Attachments	`integer`	computed
availability	Availability The date at which the applicant will be available to start working	`date`
campaign_id	Campaign	`many2one` → utm.campaign
categ_ids	Tags	`many2many` → hr.applicant.category
color	Color Index	`integer`
company_id	Company	`many2one` → res.company	computed, stored
create_date	Applied on	`datetime`	read-only
current_applicant_skill_ids	Current Applicant Skill	`one2many` → hr.applicant.skill	computed inverse: `applicant_id` added by Recruitment - Skills Management (`hr_recruitment_skills`)
date_closed	Hire Date	`datetime`	computed, stored
date_last_stage_update	Last Stage Update	`datetime`
date_open	Assigned	`datetime`	read-only
day_close	Days to Close	`float`	computed
day_open	Days to Open	`float`	computed
delay_close	Delay to Close Number of days to close	`float`	read-onlycomputed, stored
department_id	Department	`many2one` → hr.department	computed, stored
email_from	Email	`char`	computed, stored
email_normalized	Email Normalized	`char`
emp_is_active	Employee Active	`boolean`	related: `employee_id.active`
employee_id	Employee Employee linked to the applicant.	`many2one` → hr.employee
employee_name	Employee Name	`char`	related: `employee_id.name`
interviewer_ids	Interviewers	`many2many` → res.users
is_applicant_in_pool	Is Applicant In Pool	`boolean`	computed
is_pool_applicant	Is Pool Applicant	`boolean`	computed
job_id	Job Position	`many2one` → hr.job
kanban_state	Kanban State	`selection`	required Values: `normal` (In Progress), `done` (Ready for Next Stage), `waiting` (Waiting), `blocked` (Blocked)
last_stage_id	Last Stage Stage of the applicant before being in the current stage. Used for lost cases analysis.	`many2one` → hr.recruitment.stage
legend_blocked	Kanban Blocked	`char`	related: `stage_id.legend_blocked`
legend_done	Kanban Valid	`char`	related: `stage_id.legend_done`
legend_normal	Kanban Ongoing	`char`	related: `stage_id.legend_normal`
legend_waiting	Kanban Waiting	`char`	related: `stage_id.legend_waiting`
linkedin_profile	LinkedIn Profile	`char`
matching_score	Matching Score	`integer`	computed added by Recruitment - Skills Management (`hr_recruitment_skills`)
matching_skill_ids	Matching Skills	`many2many` → hr.skill	computed added by Recruitment - Skills Management (`hr_recruitment_skills`)
medium_id	Medium This displays how the applicant has reached out, e.g. via Email, LinkedIn, Website, etc.	`many2one` → utm.medium
meeting_display_date	Meeting Display Date	`date`	computed
meeting_display_text	Meeting Display Text	`char`	computed
meeting_ids	Meetings	`one2many` → calendar.event	inverse: `applicant_id`
missing_skill_ids	Missing Skills	`many2many` → hr.skill	computed added by Recruitment - Skills Management (`hr_recruitment_skills`)
partner_id	Contact	`many2one` → res.partner
partner_name	Applicant's Name	`char`
partner_phone	Phone	`char`	computed, stored
partner_phone_sanitized	Sanitized Phone Number	`char`	computed, stored
pool_applicant_id	Pool Applicant	`many2one` → hr.applicant
priority	Evaluation	`selection`	Values: `0` (Normal), `1` (Good), `2` (Very Good), `3` (Excellent)
probability	Probability	`float`
refuse_date	Refuse Date	`datetime`
refuse_reason_id	Refuse Reason	`many2one` → hr.applicant.refuse.reason
response_ids	Responses	`one2many` → survey.user_input	inverse: `applicant_id` added by Hr Recruitment Interview Forms (`hr_recruitment_survey`)
salary_expected	Expected Salary Expected by Applicant	`float`
salary_expected_extra	Expected Salary Extra Salary Expected by Applicant, extra advantages	`char`
salary_proposed	Proposed Salary Proposed by the Organisation	`float`
salary_proposed_extra	Proposed Salary Extra Salary Proposed by the Organisation, extra advantages	`char`
sequence	Sequence	`integer`
skill_ids	Skill	`many2many` → hr.skill	computed, stored added by Recruitment - Skills Management (`hr_recruitment_skills`)
source_id	Source	`many2one` → utm.source
stage_id	Stage	`many2one` → hr.recruitment.stage	computed, stored
survey_id	Survey	`many2one` → survey.survey	read-only related: `job_id.survey_id` added by Hr Recruitment Interview Forms (`hr_recruitment_survey`)
talent_pool_count	Talent Pool Count	`integer`	computed
talent_pool_ids	Talent Pools	`many2many` → hr.talent.pool
type_id	Degree	`many2one` → hr.recruitment.degree
user_email	User Email	`char`	read-only related: `user_id.email`
user_id	Recruiter	`many2one` → res.users	computed, stored
activity_calendar_event_id	Next Activity Calendar Event	`many2one` → calendar.event	computed inherited from mail.activity.mixin
activity_date_deadline	Next Activity Deadline	`date`	read-onlycomputed inherited from mail.activity.mixin
activity_exception_decoration	Activity Exception Decoration Type of the exception activity on record.	`selection`	computed Values: `warning` (Alert), `danger` (Error) inherited from mail.activity.mixin
activity_exception_icon	Icon Icon to indicate an exception activity.	`char`	computed inherited from mail.activity.mixin
activity_ids	Activities	`one2many` → mail.activity	inverse: `res_id` inherited from mail.activity.mixin
activity_state	Activity State Status based on activities Overdue: Due date is already passed Today: Activity date is today Planned: Future activities.	`selection`	computed Values: `overdue` (Overdue), `today` (Today), `planned` (Planned) inherited from mail.activity.mixin
activity_summary	Next Activity Summary	`char`	related: `activity_ids.summary` inherited from mail.activity.mixin
activity_type_icon	Activity Type Icon	`char`	related: `activity_ids.icon` inherited from mail.activity.mixin
activity_type_id	Next Activity Type	`many2one` → mail.activity.type	related: `activity_ids.activity_type_id` inherited from mail.activity.mixin
activity_user_id	Responsible User	`many2one` → res.users	read-onlycomputed inherited from mail.activity.mixin
duration_tracking	Status time JSON that maps ids from a many2one field to seconds spent	`json`	computed inherited from mail.tracking.duration.mixin
email_cc	Email cc	`char`	inherited from mail.thread.cc
has_message	Has Message	`boolean`	computed inherited from mail.thread
is_blacklisted	Blacklist If the email address is on the blacklist, the contact won't receive mass mailing anymore, from any list	`boolean`	computed inherited from mail.thread.blacklist
is_rotting	Rotting	`boolean`	computed inherited from mail.tracking.duration.mixin
message_attachment_count	Attachment Count	`integer`	computed inherited from mail.thread
message_bounce	Bounce Counter of the number of bounced emails for this contact	`integer`	inherited from mail.thread.blacklist
message_follower_ids	Followers	`one2many` → mail.followers	inverse: `res_id` inherited from mail.thread
message_has_error	Message Delivery error If checked, some messages have a delivery error.	`boolean`	computed inherited from mail.thread
message_has_error_counter	Number of errors Number of messages with delivery error	`integer`	computed inherited from mail.thread
message_has_sms_error	SMS Delivery error If checked, some messages have a delivery error.	`boolean`	computed inherited from mail.thread
message_ids	Messages	`one2many` → mail.message	inverse: `res_id` inherited from mail.thread
message_is_follower	Is Follower	`boolean`	computed inherited from mail.thread
message_main_attachment_id	Main Attachment	`many2one` → ir.attachment	inherited from mail.thread.main.attachment
message_needaction	Action Needed If checked, new messages require your attention.	`boolean`	computed inherited from mail.thread
message_needaction_counter	Number of Actions Number of messages requiring action	`integer`	computed inherited from mail.thread
message_partner_ids	Followers (Partners)	`many2many` → res.partner	computed inherited from mail.thread
my_activity_date_deadline	My Activity Deadline	`date`	read-onlycomputed inherited from mail.activity.mixin
phone_blacklisted	Blacklisted Phone is Phone Indicates if a blacklisted sanitized phone number is a phone number. Helps distinguish which number is blacklisted when there is both a mobile and phone field in a model.	`boolean`	computed inherited from mail.thread.phone
phone_mobile_search	Phone Number	`char`	inherited from mail.thread.phone
phone_sanitized	Sanitized Number Field used to store sanitized phone number. Helps speeding up searches and comparisons.	`char`	computed, stored inherited from mail.thread.phone
phone_sanitized_blacklisted	Phone Blacklisted If the sanitized phone number is on the blacklist, the contact won't receive mass mailing sms anymore, from any list	`boolean`	computed inherited from mail.thread.phone
rating_ids	Ratings	`one2many` → rating.rating	inverse: `res_id` inherited from mail.thread
rotting_days	Days Rotting Day count since this resource was last updated	`integer`	computed inherited from mail.tracking.duration.mixin
website_message_ids	Website Messages Website communication history	`one2many` → mail.message	inverse: `res_id` inherited from mail.thread
create_uid	Created by	`many2one` → res.users	read-onlyautomatic
display_name	Display Name	`char`	read-onlycomputedautomatic
id	ID	`integer`	read-onlyautomatic
write_date	Last Updated on	`datetime`	read-onlyautomatic
write_uid	Last Updated by	`many2one` → res.users	read-onlyautomatic

Relations

Models linked from this model

calendar.event: meeting_ids
hr.applicant: pool_applicant_id
hr.applicant.category: categ_ids
hr.applicant.refuse.reason: refuse_reason_id
hr.applicant.skill: applicant_skill_ids, current_applicant_skill_ids
hr.department: department_id
hr.employee: employee_id
hr.job: job_id
hr.recruitment.degree: type_id
hr.recruitment.stage: last_stage_id, stage_id
hr.skill: matching_skill_ids, missing_skill_ids, skill_ids
hr.talent.pool: talent_pool_ids
ir.attachment: attachment_ids
res.company: company_id
res.partner: partner_id
res.users: interviewer_ids, user_id
survey.survey: survey_id
survey.user_input: response_ids
utm.campaign: campaign_id
utm.medium: medium_id
utm.source: source_id

Fields of other models pointing here

applicant.get.refuse.reason: applicant_ids, duplicate_applicant_ids
applicant.send.mail: applicant_ids
calendar.event: applicant_id
hr.applicant: pool_applicant_id
hr.applicant.skill: applicant_id
hr.talent.pool: talent_ids
job.add.applicants: applicant_ids
survey.invite: applicant_id
survey.user_input: applicant_id
talent.pool.add.applicants: applicant_ids

Reading this model through the API

Odoo 19 JSON-2 API call reading the first five records with real fields of the model. Replace the instance, database and API key with your own.

curl

curl -X POST "https://your-instance.odoo.com/json/2/hr.applicant/search_read" \
  -H "Authorization: bearer $ODOO_API_KEY" \
  -H "X-Odoo-Database: your-db" \
  -H "Content-Type: application/json" \
  -d '{"domain":[],"fields":["partner_name","kanban_state","campaign_id","company_id","department_id"],"limit":5}'

Python (requests)

import requests

BASE_URL = "https://your-instance.odoo.com/json/2"
headers = {"Authorization": f"bearer {API_KEY}", "X-Odoo-Database": "your-db"}

res = requests.post(
    f"{BASE_URL}/hr.applicant/search_read",
    headers=headers,
    json={"domain": [], "fields": ["partner_name","kanban_state","campaign_id","company_id","department_id"], "limit": 5},
)
res.raise_for_status()
print(res.json())

External API access requires Odoo's Custom plan.
XML-RPC and JSON-RPC will be removed in Odoo 22 (fall 2028): use JSON-2.
The access rights and record rules of the key's user apply.

Cite this tool

Writing a tutorial, internal documentation or a forum answer? Copy this link to send your readers to the up-to-date reference.

<a href="https://aidoo.ai/en/outils/explorateur-modeles-odoo/hr-applicant">hr.applicant (Odoo 19.0)</a>

Sources

Data verified on September 23, 2026 · Odoo 19.0 Community

Have an Odoo project, or want to put your ERP to work with AI? Let's talk

Implementation, custom module development, connecting Claude or ChatGPT to your data: tell us about your context and we will reply within 24 business hours.