resource.calendar.leaves: fields, relations and API
The resource.calendar.leaves model ("Resource Time Off Detail") is a persistent model declared by the Resource module, then extended by 5 other modules. It exposes 17 fields, 11 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
resource.calendar.leaves- Label
- Resource Time Off Detail
- Type
- Persistent (models.Model)
- SQL table
resource_calendar_leaves- Origin module
- Resource (
resource) - Extended by
- hr, hr_holidays, hr_holidays_attendance, hr_work_entry, project_timesheet_holidays
- Default order (_order)
date_from
Model fields
11 own fields, 0 inherited from mixins and 6 automatic ORM fields. Click a name to get a direct link to that field.
17 of 17 fields shown
| Technical name | Label | Type | Details |
|---|---|---|---|
| calendar_id | Working Hours | many2one | computed, stored |
| company_id | Company | many2one | read-onlycomputed, stored |
| date_from | Start Date | datetime | required |
| date_to | End Date | datetime | requiredcomputed, stored |
| elligible_for_accrual_rate | Eligible for Accrual Rate If checked, this time off type will be taken into account for accruals computation. | boolean | added by Time Off ( |
| holiday_id | Time Off Request | many2one→ hr.leave | added by Time Off ( |
| name | Reason | char | |
| resource_id | Resource If empty, this is a generic time off for the company. If a resource is set, the time off is only for this resource | many2one | |
| time_type | Time Type Whether this should be computed as a time off or as work time (eg: formation) | selection | Values: |
| timesheet_ids | Analytic Lines | one2many | inverse: added by Timesheet when on Time Off ( |
| work_entry_type_id | Work Entry Type | many2one | added by Work Entries ( |
| 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
- account.analytic.line: timesheet_ids
- hr.leave: holiday_id
- hr.work.entry.type: work_entry_type_id
- res.company: company_id
- resource.calendar: calendar_id
- resource.resource: resource_id
Fields of other models pointing here
- account.analytic.line: global_leave_id
- mrp.workorder: leave_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/resource.calendar.leaves/search_read" \
-H "Authorization: bearer $ODOO_API_KEY" \
-H "X-Odoo-Database: your-db" \
-H "Content-Type: application/json" \
-d '{"domain":[],"fields":["name","date_from","date_to","calendar_id","company_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}/resource.calendar.leaves/search_read",
headers=headers,
json={"domain": [], "fields": ["name","date_from","date_to","calendar_id","company_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/resource-calendar-leaves">resource.calendar.leaves (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.