Odoo 19.0 Community · Persistent

event.registration: fields, relations and API

The event.registration model ("Event Registration") is a persistent model declared by the Events Organization module, then extended by 9 other modules. It exposes 64 fields, 34 of them declared directly on the model; 7 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: event.registration
Label: Event Registration
Type: Persistent (models.Model)
SQL table: event_registration
Origin module: Events Organization (event)
Extended by: event_product, event_sale, event_crm, event_crm_sale, mass_mailing_event, website_event, pos_event, pos_event_sale, website_event_crm
Default order (_order): id desc
Inherits from (mixins): mail.thread mail.activity.mixin pos.load.mixin

Model fields

34 own fields, 24 inherited from mixins and 6 automatic ORM fields. Click a name to get a direct link to that field.

Hide inherited fields

64 of 64 fields shown

Technical name	Label	Type	Details
active	Active	`boolean`
barcode	Barcode	`char`	read-only
company_id	Company	`many2one` → res.company	related: `event_id.company_id`
company_name	Company Name	`char`	computed, stored
date_closed	Attended Date	`datetime`	computed, stored
email	Email	`char`	computed, stored
event_begin_date	Event Start Date	`datetime`	computed
event_date_range	Date Range	`char`	computed
event_end_date	Event End Date	`datetime`	computed
event_id	Event	`many2one` → event.event	required
event_organizer_id	Event Organizer	`many2one` → res.partner	read-only related: `event_id.organizer_id`
event_slot_id	Slot	`many2one` → event.slot
event_ticket_id	Ticket Type	`many2one` → event.event.ticket
event_user_id	Event Responsible	`many2one` → res.users	read-only related: `event_id.user_id`
is_multi_slots	Is Event Multi Slots	`boolean`	related: `event_id.is_multi_slots`
lead_count	# Leads	`integer`	computed added by Event CRM (`event_crm`)
lead_ids	Leads	`many2many` → crm.lead	read-only added by Event CRM (`event_crm`)
mail_registration_ids	Scheduler Emails	`one2many` → event.mail.registration	read-only inverse: `registration_id`
name	Attendee Name	`char`	computed, stored
partner_id	Booked by	`many2one` → res.partner
phone	Phone	`char`	computed, stored
pos_order_id	PoS Order	`many2one` → pos.order	related: `pos_order_line_id.order_id` added by POS - Event (`pos_event`)
pos_order_line_id	PoS Order Line	`many2one` → pos.order.line	added by POS - Event (`pos_event`)
registration_answer_choice_ids	Attendee Selection Answers	`one2many` → event.registration.answer	inverse: `registration_id`
registration_answer_ids	Attendee Answers	`one2many` → event.registration.answer	inverse: `registration_id`
registration_properties	Properties	`properties`
sale_order_id	Sales Order	`many2one` → sale.order	added by Events Sales (`event_sale`)
sale_order_line_id	Sales Order Line	`many2one` → sale.order.line	added by Events Sales (`event_sale`)
sale_status	Sale Status	`selection`	read-onlycomputed, stored Values: `to_pay` (Not Sold), `sold` (Sold), `free` (Free) added by Events Product (`event_product`)
state	Status Unconfirmed: registrations in a pending state waiting for an action (specific case, notably with sale status) Registered: registrations considered taken by a client Attended: registrations for which the attendee attended the event Cancelled: registrations cancelled manually	`selection`	read-onlycomputed, stored Values: `draft` (Unconfirmed), `open` (Registered), `done` (Attended), `cancel` (Cancelled)
utm_campaign_id	Campaign	`many2one` → utm.campaign	computed, stored
utm_medium_id	Medium	`many2one` → utm.medium	computed, stored
utm_source_id	Source	`many2one` → utm.source	computed, stored
visitor_id	Visitor	`many2one` → website.visitor	added by Events (`website_event`)
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
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` → 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_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
rating_ids	Ratings	`one2many` → rating.rating	inverse: `res_id` inherited from mail.thread
website_message_ids	Website Messages Website communication history	`one2many` → mail.message	inverse: `res_id` inherited from mail.thread
create_date	Created on	`datetime`	read-onlyautomatic
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

crm.lead: lead_ids
event.event: event_id
event.event.ticket: event_ticket_id
event.mail.registration: mail_registration_ids
event.registration.answer: registration_answer_choice_ids, registration_answer_ids
event.slot: event_slot_id
pos.order: pos_order_id
pos.order.line: pos_order_line_id
res.company: company_id
res.partner: event_organizer_id, partner_id
res.users: event_user_id
sale.order: sale_order_id
sale.order.line: sale_order_line_id
utm.campaign: utm_campaign_id
utm.medium: utm_medium_id
utm.source: utm_source_id
website.visitor: visitor_id

Fields of other models pointing here

crm.lead: registration_ids
event.mail: last_registration_id
event.mail.registration: registration_id
event.mail.slot: last_registration_id
event.registration.answer: registration_id
event.sale.report: event_registration_id
registration.editor.line: registration_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

curl -X POST "https://your-instance.odoo.com/json/2/event.registration/search_read" \
  -H "Authorization: bearer $ODOO_API_KEY" \
  -H "X-Odoo-Database: your-db" \
  -H "Content-Type: application/json" \
  -d '{"domain":[],"fields":["name","event_id","state","company_id","event_organizer_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}/event.registration/search_read",
    headers=headers,
    json={"domain": [], "fields": ["name","event_id","state","company_id","event_organizer_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/event-registration">event.registration (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.