event.event.ticket: fields, relations and API
The event.event.ticket model ("Event Ticket") is a persistent model declared by the Events Organization module, then extended by 4 other modules. It exposes 37 fields, 19 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 20 JSON-2 API call.
Model identity
- Technical name
event.event.ticket- Label
- Event Ticket
- Type
- Persistent (models.Model)
- SQL table
event_event_ticket- Origin module
- Events Organization (
event) - Extended by
- event_product, event_sale, pos_event, website_event_sale
- Default order (_order)
event_id, sequence, price, name, id- Inherits from (mixins)
- event.type.ticketpos.load.mixin
Model fields
19 own fields, 12 inherited from mixins and 6 automatic ORM fields. Click a name to get a direct link to that field.
37 of 37 fields shown
| Technical name | Label | Type | Details |
|---|---|---|---|
| color | Color | char | |
| company_id | Company | many2one | related: |
| end_sale_datetime | Registration End | datetime | |
| entry_limit | Entry Limit Enable multi-entry tickets - Set to 0 or 1 to disable. - Enter 2 or more to define the maximum number of allowed entries. | integer | |
| event_id | Event | many2one | required |
| event_type_id | Event Type | many2one | |
| is_expired | Is Expired | boolean | computed |
| is_launched | Are sales launched | boolean | computed |
| is_sold_out | Sold Out Whether seats are not available for this ticket. | boolean | computed |
| limit_max_per_order | Limit per Order Maximum of this product per order. Set to 0 to ignore this rule | integer | |
| registration_ids | Registrations | one2many | inverse: |
| sale_available | Is Available Whether it is possible to sell these tickets | boolean | computed |
| seats_available | Available Seats | integer | computed |
| seats_reserved | Reserved Seats | integer | computed |
| seats_taken | Taken Seats | integer | computed |
| seats_used | Used Seats | integer | computed |
| start_sale_datetime | Registration Start | datetime | |
| total_price_incl | Total Price include | float | computed added by Events Product ( |
| total_price_reduce_taxinc | Total Price Reduce Tax inc | float | computed added by Events Product ( |
| additional_product_ids | Additional Products Select products to include with each registration. They will also show up separately on Sale Orders. | many2many | inherited from event.type.ticket |
| currency_id | Currency | many2one | related: inherited from event.type.ticket |
| description | Description A description of the ticket that you want to communicate to your customers. | text | computed, storedtranslatable inherited from event.type.ticket |
| name | Name | char | requiredtranslatable inherited from event.type.ticket |
| price | Ticket Price | float | computed, stored inherited from event.type.ticket |
| price_reduce | Price Reduce | float | computed inherited from event.type.ticket |
| product_id | Product | many2one | required inherited from event.type.ticket |
| seats_limited | Limit Attendees | boolean | read-onlycomputed, stored inherited from event.type.ticket |
| seats_max | Maximum Attendees Define the number of available tickets. If you have too many registrations you will not be able to sell tickets anymore. Set 0 to ignore this rule set as unlimited. | integer | inherited from event.type.ticket |
| sequence | Sequence | integer | inherited from event.type.ticket |
| total_price | Total Price Price at which this ticket will be sold, which takes into account the Ticket Price and the price of every Additional Product | float | computed inherited from event.type.ticket |
| total_price_reduce | Total Price Reduce | float | computed inherited from event.type.ticket |
| 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
- event.type: event_type_id
- res.company: company_id
Fields of other models pointing here
- event.event.configurator: event_ticket_id
- event.registration: event_ticket_id
- event.sale.report: event_ticket_id
- pos.order.line: event_ticket_id
- registration.editor.line: event_ticket_id
- sale.order.line: event_ticket_id
Reading this model through the API
Odoo 20 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.event.ticket/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","company_id","event_type_id","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.event.ticket/search_read",
headers=headers,
json={"domain": [], "fields": ["name","event_id","company_id","event_type_id","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-event-ticket">event.event.ticket (Odoo 20.0)</a>Sources
Data verified on September 25, 2026 · Odoo 20.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.