resource.calendar: fields, relations and API
The resource.calendar model ("Resource Working Time") is a persistent model declared by the Resource module, then extended by 3 other modules. It exposes 28 fields, 22 of them declared directly on the model; 23 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
resource.calendar- Label
- Resource Working Time
- Type
- Persistent (models.Model)
- SQL table
resource_calendar- Origin module
- Resource (
resource) - Extended by
- hr, hr_work_entry, hr_holidays
Model fields
22 own fields, 0 inherited from mixins and 6 automatic ORM fields. Click a name to get a direct link to that field.
28 of 28 fields shown
| Technical name | Label | Type | Details |
|---|---|---|---|
| active | Active If the active field is set to false, it will allow you to hide the Working Time without removing it. | boolean | |
| associated_leaves_count | Time Off Count | integer | computed added by Time Off ( |
| attendance_ids | Working Time | one2many | computed, stored inverse: |
| calendar_type | Calendar Type - Fixed: a weekly attendance pattern that repeats identically every week. - Variable: attendances set on specific dates rather than a repeating weekly pattern, such as a one-off schedule or a multi-week rotation. - Undefined: no predefined slots at all. The resource can work whenever it wants, optionally up to an hours target. | selection | required Values: |
| company_id | Company | many2one | |
| country_code | Country Code | char | related: |
| country_id | Country | many2one | related: |
| days_per_week | Days per Week | float | computed, stored |
| employees_count | Employees Count | integer | computed added by Employees ( |
| full_time_required_hours | Full Time Equivalent Number of hours to work on the company schedule to be considered as fulltime. | float | computed, stored |
| global_leave_ids | Global Time Off | one2many | computed, stored inverse: |
| hours_per_day | Average Hour per Day Average hours per day a resource is supposed to work with this calendar. | float | computed, stored |
| hours_per_week | Hours per Week | float | computed, stored |
| is_fulltime | Is Full Time | boolean | computed |
| leave_accrual_plan_id | Accrual Plan | many2one | added by Time Off ( |
| leave_ids | Time Off | one2many | inverse: |
| material_resources_count | Material Resources Count | integer | computed added by Employees ( |
| name | Name | char | required |
| reference_calendar_id | Reference Calendar Reference working hours used to compute the full-time equivalent. | many2one | |
| version_ids | Version | one2many | read-only inverse: added by Employees ( |
| work_resources_count | Work Resources count | integer | computed |
| work_time_rate | Work Time Rate Work time rate versus full time working schedule, should be between 0 and 100 %. | float | computed, stored |
| 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
- hr.leave.accrual.plan: leave_accrual_plan_id
- hr.version: version_ids
- res.company: company_id
- res.country: country_id
- resource.calendar: reference_calendar_id
- resource.calendar.attendance: attendance_ids
- resource.calendar.leaves: global_leave_ids, leave_ids
Fields of other models pointing here
- base.automation: trg_date_calendar_id
- delivery.carrier: delivery_calendar_id
- hr.attendance: resource_calendar_id
- hr.employee: resource_calendar_id
- hr.employee.public: resource_calendar_id
- hr.leave: resource_calendar_id
- hr.leave.attendance.report: schedule_id
- hr.leave.mandatory.day: resource_calendar_id
- hr.payroll.structure.type: default_resource_calendar_id
- hr.time.rule: resource_calendar_id
- hr.version: resource_calendar_id
- mrp.workcenter: resource_calendar_id
- pos.preset: resource_calendar_id
- project.project: resource_calendar_id
- res.company: resource_calendar_id
- res.config.settings: resource_calendar_id
- res.users: resource_calendar_id
- resource.calendar: reference_calendar_id
- resource.calendar.attendance: calendar_id
- resource.calendar.leaves: calendar_id
- resource.mixin: resource_calendar_id
- resource.resource: calendar_id
- stock.warehouse: opening_hours
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/resource.calendar/search_read" \
-H "Authorization: bearer $ODOO_API_KEY" \
-H "X-Odoo-Database: your-db" \
-H "Content-Type: application/json" \
-d '{"domain":[],"fields":["name","calendar_type","company_id","country_id","leave_accrual_plan_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/search_read",
headers=headers,
json={"domain": [], "fields": ["name","calendar_type","company_id","country_id","leave_accrual_plan_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">resource.calendar (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.