survey.user_input: fields, relations and API
The survey.user_input model ("Survey User Input") is a persistent model declared by the Surveys module, then extended by 4 other modules. It exposes 61 fields, 31 of them declared directly on the model; 1 field from other models points 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.
Model identity
- Technical name
survey.user_input- Label
- Survey User Input
- Type
- Persistent (models.Model)
- SQL table
survey_user_input- Origin module
- Surveys (
survey) - Extended by
- hr_recruitment_survey, hr_skills_survey, survey_crm, website_slides_survey
- Default order (_order)
create_date desc- Display field (_rec_name)
survey_id- Inherits from (mixins)
- mail.threadmail.activity.mixin
Model fields
31 own fields, 24 inherited from mixins and 6 automatic ORM fields. Click a name to get a direct link to that field.
61 of 61 fields shown
| Technical name | Label | Type | Details |
|---|---|---|---|
| access_token | Identification token | char | requiredread-only |
| applicant_id | Applicant | many2one | added by Hr Recruitment Interview Forms ( |
| attempts_count | Attempts Count | integer | computed |
| attempts_limit | Number of attempts | integer | related: |
| attempts_number | Attempt n° | integer | computed |
| deadline | Deadline Datetime until customer can open the survey and submit answers | datetime | |
char | read-only | ||
| end_datetime | End date and time | datetime | read-only |
| invite_token | Invite token | char | read-only |
| is_attempts_limited | Limited number of attempts | boolean | related: |
| is_session_answer | Is in a Session Is that user input part of a survey session or not. | boolean | |
| lang_id | Language | many2one→ res.lang | |
| last_displayed_page_id | Last displayed question/page | many2one | |
| lead_id | Lead | many2one→ crm.lead | added by Survey CRM ( |
| nickname | Nickname Attendee nickname, mainly used to identify them in the survey session leaderboard. | char | |
| partner_id | Contact | many2one | read-only |
| predefined_question_ids | Predefined Questions | many2many | read-only |
| question_time_limit_reached | Question Time Limit Reached | boolean | computed |
| scoring_percentage | Score (%) | float | computed, stored |
| scoring_success | Quiz Passed | boolean | computed, stored |
| scoring_total | Total Score | float | computed, stored |
| scoring_type | Scoring | selection | related: |
| slide_id | Related course slide The related course slide when there is no membership information | many2one | added by Course Certifications ( |
| slide_partner_id | Subscriber information Slide membership information for the logged in user | many2one | added by Course Certifications ( |
| start_datetime | Start date and time | datetime | read-only |
| state | Status | selection | read-only Values: |
| survey_first_submitted | Survey First Submitted | boolean | |
| survey_id | Survey | many2one | requiredread-only |
| survey_time_limit_reached | Survey Time Limit Reached | boolean | computed |
| test_entry | Test Entry | boolean | read-only |
| user_input_line_ids | Answers | one2many | inverse: |
| activity_calendar_event_id | Next Activity Calendar Event | many2one | 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: 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 | inverse: 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: inherited from mail.activity.mixin |
| activity_summary | Next Activity Summary | char | related: inherited from mail.activity.mixin |
| activity_type_icon | Activity Type Icon | char | related: inherited from mail.activity.mixin |
| activity_type_id | Next Activity Type | many2one | related: inherited from mail.activity.mixin |
| activity_user_id | Responsible User | many2one | read-onlycomputed inherited from mail.activity.mixin |
| has_message | Has Message | boolean | computed inherited from mail.thread |
| message_attachment_count | Attachment Count | integer | computed inherited from mail.thread |
| message_follower_ids | Followers | one2many | inverse: 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 | inverse: inherited from mail.thread |
| message_is_follower | Is Follower | boolean | computed inherited from mail.thread |
| 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 | computed inherited from mail.thread |
| my_activity_date_deadline | My Activity Deadline | date | read-onlycomputed inherited from mail.activity.mixin |
| rating_ids | Ratings | one2many | inverse: inherited from mail.thread |
| website_message_ids | Website Messages Website communication history | one2many | inverse: inherited from mail.thread |
| create_date | Created on | datetime | read-onlyautomatic |
| create_uid | Created by | many2one | 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 | read-onlyautomatic |
Relations
Models linked from this model
- crm.lead: lead_id
- hr.applicant: applicant_id
- res.lang: lang_id
- res.partner: partner_id
- slide.slide: slide_id
- slide.slide.partner: slide_partner_id
- survey.question: last_displayed_page_id, predefined_question_ids
- survey.survey: survey_id
- survey.user_input.line: user_input_line_ids
Fields of other models pointing here
- survey.user_input.line: user_input_id
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 -X POST "https://your-instance.odoo.com/json/2/survey.user_input/search_read" \
-H "Authorization: bearer $ODOO_API_KEY" \
-H "X-Odoo-Database: your-db" \
-H "Content-Type: application/json" \
-d '{"domain":[],"fields":["survey_id","access_token","state","applicant_id","lang_id"],"limit":5}'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}/survey.user_input/search_read",
headers=headers,
json={"domain": [], "fields": ["survey_id","access_token","state","applicant_id","lang_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/survey-user_input">survey.user_input (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.