In the Rentman API Changelog, you’ll find an overview of all updates made to the API. Additional documentation and examples can be found by following this link.

Check out our regular Rentman Changelog here to read about updates in your Rentman workspace.

API Changelog 1.13.0

01.06.2026

New Features

All Endpoints

• Added: expand parameter – allows expanding related resources inline in the response, reducing the need for additional requests. Pass one or more resource names as a comma-separated list to include their full data instead of just the reference ID.

Bug Fixes / Corrections

Corrected the nullable declaration on created and modified fields for the following resources. These fields were already always present in practice; the spec now reflects that accurately.

Files

• Changed: created – no longer declared as nullable (was string | null, now string)
• Changed: modified – no longer declared as nullable (was string | null, now string)

Subprojects

• Changed: created – no longer declared as nullable (was string | null, now string)
• Changed: modified – no longer declared as nullable (was string | null, now string)

Tasks

• Changed: created – no longer declared as nullable (was string | null, now string)
• Changed: modified – no longer declared as nullable (was string | null, now string)

API Changelog 1.12.0

26.05.2026

New Endpoints

Tasks can now be read and created via linked resource endpoints, and managed directly via the /tasks resource.

GET    /tasks
POST   /tasks
GET    /tasks/{id}
PUT    /tasks/{id}
DELETE /tasks/{id}
GET    /tasks/{id}/subtasks
POST   /tasks/{id}/subtasks
GET    /tasks/{id}/taskassignments
POST   /tasks/{id}/taskassignments
GET    /tasks/{id}/files
GET    /tasks/{id}/file_folders

GET    /taskstatuses
POST   /taskstatuses
GET    /taskstatuses/{id}
PUT    /taskstatuses/{id}
DELETE /taskstatuses/{id}

GET    /subtasks
GET    /subtasks/{id}
PUT    /subtasks/{id}
DELETE /subtasks/{id}

GET    /taskassignments
GET    /taskassignments/{id}
PUT    /taskassignments/{id}
DELETE /taskassignments/{id}

Tasks linked to other resources:

GET    /contactpersons/{id}/tasks
POST   /contactpersons/{id}/tasks
GET    /contacts/{id}/tasks
POST   /contacts/{id}/tasks
GET    /contracts/{id}/tasks
POST   /contracts/{id}/tasks
GET    /crew/{id}/tasks
POST   /crew/{id}/tasks
GET    /equipment/{id}/tasks
POST   /equipment/{id}/tasks
GET    /invoices/{id}/tasks
POST   /invoices/{id}/tasks
GET    /projects/{id}/tasks
POST   /projects/{id}/tasks
GET    /purchaseorders/{id}/tasks
POST   /purchaseorders/{id}/tasks
GET    /quotes/{id}/tasks
POST   /quotes/{id}/tasks
GET    /repairs/{id}/tasks
POST   /repairs/{id}/tasks
GET    /serialnumbers/{id}/tasks
POST   /serialnumbers/{id}/tasks
GET    /subrentals/{id}/tasks
POST   /subrentals/{id}/tasks
GET    /suppliers/{id}/tasks
POST   /suppliers/{id}/tasks
GET    /vehicles/{id}/tasks
POST   /vehicles/{id}/tasks

Purchase Orders are now available via the API.

GET    /purchaseorders
GET    /purchaseorders/{id}
GET    /purchaseorders/{id}/files
GET    /purchaseorders/{id}/file_folders
GET    /purchaseorders/{id}/invoicelines
GET    /purchaseorders/{id}/purchaseordercosts
GET    /purchaseorders/{id}/purchaseorderglobalcosts
GET    /purchaseordercosts
GET    /purchaseordercosts/{id}
GET    /purchaseorderglobalcosts
GET    /purchaseorderglobalcosts/{id}

Extra Input Fields (custom fields configuration) are now readable via the API.

GET    /extrainputfields
GET    /extrainputfields/{id}

New Methods on Existing Endpoints

/equipment/{id}
- Added: PUT – Equipment items can now be updated via the API.

/folders and /folders/{id}
- Added: POST – Folders can now be created via the API.
- Added: PUT – Folders can now be updated via the API.

New Fields

Projects (/projects, /subprojects)

- Added: estimated_cost – GENERATED FIELD. Not visible in collection responses unless explicitly requested.
- Added: planned_cost – GENERATED FIELD. Not visible in collection responses unless explicitly requested.
- Added: actual_cost – GENERATED FIELD. Not visible in collection responses unless explicitly requested.

Files and File Folders (/files, /file_folders)

- Added: parent_api_path – GENERATED FIELD. The API path of the parent item.

Invoice Lines (/invoicelines)

- Added: parent_api_path – GENERATED FIELD. The API path of the parent item.

Field Changes

Equipment (/equipment)

- Changed: is_physical – Type corrected from boolean to string enum. Possible values: "Virtual package", "Physical equipment".
- Changed: rental_sales – Type corrected from boolean to string enum. Possible values: "Sale", "Rental".
- Changed: stock_management – Type corrected from boolean to string enum. Possible values: "Exclude from stock tracking", "Track stock".
- Changed: strict_container_content – Type corrected from boolean to string enum. Possible values: "Unrestricted", "Strict".

Equipment Set Contents (/equipment/{id}/setcontents)

- Changed: is_fixed – Type corrected from boolean to string enum. Possible values: "Available outside this combination", "Reserved from stock".
- Changed: is_physically_connected – Type corrected from boolean to string enum. Possible values: "Will be removed when emptying combinations", "Will remain in the combination when emptying combinations".

Files and File Folders (/files, /file_folders)

- Changed: item – Type corrected from string to integer (numeric ID of the linked item).
- Changed: itemtype – Type corrected from integer to string enum with allowed item type values.

Invoice Lines (/invoicelines)

- Changed: item – Type corrected from string to integer (numeric ID of the linked item).

Leave Types (/leavetypes)

- Changed: is_labor – Type corrected from boolean to string enum. Possible values: "leave", "worked".

Repairs (/repairs)

- Changed: is_usable – Type corrected from boolean to string enum. Possible values: "take_from_stock", "keep_usable".

Vehicles (/vehicles)

- Changed: multiple – Type corrected from boolean to string enum. Possible values: "plannable_once", "plannable_multi".

Project Functions and Function Groups

- Changed: planperiod_start_schedule_is_start, planperiod_end_schedule_is_start, usageperiod_start_schedule_is_start, usageperiod_end_schedule_is_start – Type corrected from boolean to string enum. Possible values: "is_start", "is_end".

Bug Fixes / Corrections

Project Cost, Project Crew, Project Vehicle, Project Function Group responses

- Fixed: created and modified fields were incorrectly typed as nullable date-time; corrected to non-nullable string.

API Changelog 1.11.0

01.05.2026

New Endpoints

• POST /equipment – Create a new Equipment item

API Changelog 1.10.0

30.04.2026

API Changelog – Version 1.9.0

07.04.2026

Field Changes

This update introduces new fields to the repairs endpoint, improving tracking and handling of repair workflows.

repairs

- Added:

repair_status
Indicates the current status of the repair. Possible values: in-progress, completed, unrepairable.

unrepairable_of
References another repair record when a repair is marked as partially unrepairable.
This field is populated when an existing repair is split into two records because part of the quantity cannot be repaired.

API Changelog – Version 1.8.0

25.02.2026

Item Limit Increase

The maximum number of items per collection request has been increased from 300 to 1500. The default remains 300 when no limit parameter is specified.

Pagination Overhaul

Cursor-based pagination is now the default pagination method for collection requests. Collection responses now include a next_page_url field that points to the next page of results.

How it works

• Make your initial request with an optional limit parameter (default: 300, max: 1500)
• Follow the next_page_url from each response to get the next page
• When the last page is reached, next_page_url will be null
• The cursor parameter in the URL is an opaque token — do not construct or modify it manually

Offset-based pagination

Offset-based pagination using the offset parameter is still available when sorting by a column other than id. When offset is used, next_page_url is not available and you must calculate page offsets yourself.

New Endpoints

 /invitations
 - GET /invitations – Retrieve a list of sent crew invitations
 - GET /invitations/{id} – Retrieve a specific invitation by ID
 - GET /crew/{id}/invitations – Retrieve invitations linked to a crew member

New Fields

contacts
 - Added: mailing_extra_address_line, visit_extra_address_line, invoice_extra_address_line – Extra address line fields for mailing, visit, and invoice addresses

equipment
 - Added: strict_container_content – Determines whether a combination can contain actual content that is not part of the default content. Values: Unrestricted, Strict
 - Renamed: qrcodes → QR codes / RFID, qrcodes_of_serial_numbers → QR codes / RFID serial numbers

invoices
 - Added: integration_reference_id

projectcrew
 - Added: cost_accommodation, cost_catering, cost_travel, cost_other – Detailed cost breakdown fields for crew planning

projectcrew (rates)
 - Added: cost_accommodation, cost_catering, cost_travel, cost_other, price_accommodation, price_catering, price_travel, price_other – Detailed cost and price breakdown fields for crew rates

projects
 - Added: contact_phone, location_phone, is_paid

API Changelog – Version 1.7.0

13.11.2025

Global Changes

OpenAPI Specification (OAS) overhaul

The OpenAPI specification file has been completely reworked to improve consistency, type safety, and SDK/client generation.

What’s improved

• Request and response objects are now defined as reusable components
• Collection and item responses share the same component definitions
• Request and response schemas are fully typed
• Endpoint paths have clearer names and descriptions
• Response status codes are more completely defined per endpoint

Why this matters

• Easier import into API clients (for example, Postman or Insomnia)
• Improved SDK generation
• More predictable request and response structures

Important note

• Some endpoints may return 403 responses due to rate limiting. These responses are not always explicitly listed in individual endpoint definitions.

New Project Endpoints (BETA)

As part of our ongoing API expansion, we’ve introduced endpoints for project creation and setup.

These endpoints are currently in BETA.
The API surface and available fields may change in future releases.

• POST /projects
  Creates a project. Only a limited subset of project fields is currently supported.
• POST /projects/{id}/subprojects
  Creates an additional subproject. When creating a project, one subproject is automatically created.
• POST /projects/{id}/projectfunctiongroups
• POST /projects/{id}/projectfunctions

File Folder Endpoints

Files can now be organised into folders, similar to a file system or Google Drive–style structure.

Global folder access

• GET /file_folders
• GET /file_folders/{id}

Resource-specific folder access

• GET /contactpersons/{id}/file_folders
• GET /contacts/{id}/file_folders

New Endpoints

File folders 

• This endpoint exposes the folders that files can be in. A file folder is attached in the user interface to another item, e.g. a project or an equipment item, this is done using the item and itemtype field.

New Fields

Folders

• Related to the above endpoint, displays on all file items break_duration_with_start_end: duration of breaks when the break is set up to have precise start and end times. Available on all time registration endpoints

API Changelog – Version 1.6.17

06.08.2025

Field Changes

This update introduces several new fields to existing endpoints, enhancing data retrieval and creation capabilities.

contacts
- Added: image - A new field to link an image to a contact
- The description for travel time has been updated to clarify that the value is in minutes

costs
- Added: quantity, discount & order fields have been added to better define cost items within a project

folders
- The itemtype field's enum list has been expanded to include default function, allowing default functions to be organized into folders

project requests
- Added: linked_contact_person - This field allows for directly linking an existing contact person when creating or updating a project request

projects
- Added: equipment_period_from & equipment_preriod_to - These are new generated fields showing the start and end dates of the equipment usage period for the entire project

subprojects
- Added: equipment_period_from & equipment_preriod_to - Similar to the projects endpoint, these generated fields specify the equipment usage period for the individual subproject

API Changelog – Version 1.6.16

14.05.2025

New Endpoints

/leavemutation
POST – Create a new leave mutation
GET – Retrieve a list of leave mutations

/leavemutation/{id}
GET – Retrieve a specific leave mutation by ID

/leaverequest
POST – Create a new leave request
GET – Retrieve a list of leave requests

/leaverequest/{id}
GET – Retrieve a specific leave request by ID
PUT – Update an existing leave request

/leavetypes
GET – Retrieve available leave types

/leavetypes/{id}
GET – Retrieve a specific leave type by ID

/leaverequest/{id}/timeregistration
POST – Create a time registration linked to a leave request
GET – Retrieve time registrations linked to a leave request

/timeregistration
POST – Create a new time registration
PUT – Update an existing time registration
DELETE – Delete a time registration

Field Changes

costs
verkoopprijs → sale_price
inkoopprijs → purchase_price

invoices
Added: finalized
aanmaningen_verstuurd → payment_reminder_sent
laatste_aanmaning_verstuurd → final_payment_reminder_sent
betaaldatum → payment_date

Nullable Field Correction

The following fields were previously listed as nullable, but were never actually nullable. This has now been corrected in the documentation:

crewavailability
start
end
recurrence_weekday

stockmutation
date
stock_location