event.slot: fields, relations and API
The event.slot model ("Event Slot") is a persistent model declared by the Events Organization module, then extended by 2 other modules. It exposes 20 fields, 14 of them declared directly on the model; 6 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.slot- Label
- Event Slot
- Type
- Persistent (models.Model)
- SQL table
event_slot- Origin module
- Events Organization (
event) - Extended by
- website_event, pos_event
- Default order (_order)
event_id, date, start_hour, end_hour, id- Inherits from (mixins)
- pos.load.mixin
Model fields
14 own fields, 0 inherited from mixins and 6 automatic ORM fields. Click a name to get a direct link to that field.
20 of 20 fields shown
| Technical name | Label | Type | Details |
|---|---|---|---|
| color | Color | integer | |
| date | Date | date | required |
| date_tz | Date Tz | selection | related: |
| end_datetime | End Datetime | datetime | computed, stored |
| end_hour | Ending Hour Expressed in the event timezone. | float | required |
| event_id | Event | many2one | required |
| is_sold_out | Sold Out Whether seats are sold out for this slot. | boolean | computed |
| registration_ids | Attendees | one2many | inverse: |
| seats_available | Available Seats | integer | read-onlycomputed |
| seats_reserved | Number of Registrations | integer | read-onlycomputed |
| seats_taken | Number of Taken Seats | integer | read-onlycomputed |
| seats_used | Number of Attendees | integer | read-onlycomputed |
| start_datetime | Start Datetime | datetime | computed, stored |
| start_hour | Starting Hour Expressed in the event timezone. | float | 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.registration: registration_ids
Fields of other models pointing here
- event.event.configurator: event_slot_id
- event.mail.slot: event_slot_id
- event.registration: event_slot_id
- event.sale.report: event_slot_id
- registration.editor.line: event_slot_id
- sale.order.line: event_slot_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.slot/search_read" \
-H "Authorization: bearer $ODOO_API_KEY" \
-H "X-Odoo-Database: your-db" \
-H "Content-Type: application/json" \
-d '{"domain":[],"fields":["date","end_hour","event_id","start_hour","color"],"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.slot/search_read",
headers=headers,
json={"domain": [], "fields": ["date","end_hour","event_id","start_hour","color"], "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-slot">event.slot (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.