event.mail: fields, relations and API
The event.mail model ("Event Automated Mailing") is a persistent model declared by the Events Organization module, then extended by 1 other module. It exposes 21 fields, 15 of them declared directly on the model; 2 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.
Model identity
- Technical name
event.mail- Label
- Event Automated Mailing
- Type
- Persistent (models.Model)
- SQL table
event_mail- Origin module
- Events Organization (
event) - Extended by
- event_sms
- Display field (_rec_name)
event_id
Model fields
15 own fields, 0 inherited from mixins and 6 automatic ORM fields. Click a name to get a direct link to that field.
21 of 21 fields shown
| Technical name | Label | Type | Details |
|---|---|---|---|
| error_datetime | Last Error | datetime | |
| event_id | Event | many2one | required |
| interval_nbr | Interval | integer | |
| interval_type | Trigger Indicates when the communication is sent. If the event has multiple slots, the interval is related to each time slot instead of the whole event. | selection | required Values: |
| interval_unit | Unit | selection | required Values: |
| last_registration_id | Last Attendee | many2one | |
| mail_count_done | # Sent | integer | read-only |
| mail_done | Sent | boolean | read-only |
| mail_registration_ids | Mail Registration Communication related to event registrations | one2many | inverse: |
| mail_slot_ids | Mail Slot Slot-based communication | one2many | inverse: |
| mail_state | Global communication Status | selection | computed Values: |
| notification_type | Send | selection | computed Values: |
| scheduled_date | Schedule Date | datetime | computed, stored |
| sequence | Display order | integer | |
| template_ref | Template | reference | required |
| 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
- event.event: event_id
- event.mail.registration: mail_registration_ids
- event.mail.slot: mail_slot_ids
- event.registration: last_registration_id
Fields of other models pointing here
- event.mail.registration: scheduler_id
- event.mail.slot: scheduler_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/event.mail/search_read" \
-H "Authorization: bearer $ODOO_API_KEY" \
-H "X-Odoo-Database: your-db" \
-H "Content-Type: application/json" \
-d '{"domain":[],"fields":["event_id","interval_type","interval_unit","template_ref","last_registration_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}/event.mail/search_read",
headers=headers,
json={"domain": [], "fields": ["event_id","interval_type","interval_unit","template_ref","last_registration_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-mail">event.mail (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.