Rentman

Delete Accessory item. A successful delete returns no content. via DELETE /accessories/{id}

Delete Alternative item. A successful delete returns no content. via DELETE /alternatives/{id}

Delete AppointmentCrew item. A successful delete returns no content. via DELETE /appointmentcrew/{id}

Delete Appointment item. A successful delete returns no content. via DELETE /appointments/{id}

Delete ContactPerson item. A successful delete returns no content. via DELETE /contactpersons/{id}

Delete Contact item. A successful delete returns no content. via DELETE /contacts/{id}

Delete ProjectCost item. A successful delete returns no content. via DELETE /costs/{id}

Delete CrewAvailability item. A successful delete returns no content. via DELETE /crewavailability/{id}

Delete EquipmentSetContent item. A successful delete returns no content. via DELETE /equipmentsetscontent/{id}

Delete ProjectRequestEquipment item. A successful delete returns no content. via DELETE /projectrequestequipment/{id}

Delete ProjectRequest item. A successful delete returns no content. via DELETE /projectrequests/{id}

Delete SerialNumber item. A successful delete returns no content. via DELETE /serialnumbers/{id}

Delete StockMovement item. A successful delete returns no content. via DELETE /stockmovements/{id}

Delete Subtask item. A successful delete returns no content. via DELETE /subtasks/{id}

Delete Supplier item. A successful delete returns no content. via DELETE /suppliers/{id}

Delete TaskAssignment item. A successful delete returns no content. via DELETE /taskassignments/{id}

Delete Task item. A successful delete returns no content. via DELETE /tasks/{id}

Delete TaskStatus item. A successful delete returns no content. via DELETE /taskstatuses/{id}

Delete TimeRegistration item. A successful delete returns no content. via DELETE /timeregistration/{id}

Delete Vehicle item. A successful delete returns no content. via DELETE /vehicles/{id}

Get Accessory collection -- Represents accessories of an equipment item. Each equipment can have multiple accessories. Accessories are equipment items themselves. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /accessories

Get Accessory item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /accessories/{id}

Get ActualContent collection -- Represents the actual content of serialized physical combinations. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /actualcontent

Get ActualContent item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /actualcontent/{id}

Get Alternative collection -- Represents alternatives of an equipment item. Each equipment can have multiple alternatives. Alternatives are equipment items themselves. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /alternatives

Get Alternative item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /alternatives/{id}

Get AppointmentCrew collection -- With this endpoint, you could retrieve which crew member is linked to an appointment. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /appointmentcrew

Get AppointmentCrew item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /appointmentcrew/{id}

Get Appointment collection -- With this endpoint, you could read, write, update and delete appointments. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /appointments

Get Appointment item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /appointments/{id}

Get AppointmentCrew collection -- With this endpoint, you could retrieve which crew member is linked to an appointment. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /appointments/{id}/appointmentcrew

Get ContactPerson collection -- Represents a person or department within a Contact. A Person item is always associated with one Contact. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /contactpersons

Get ContactPerson item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /contactpersons/{id}

Get FileFolder collection -- 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. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /contactpersons/{id}/file_folders

Get File collection -- All user-generated documents and uploaded files are available in this endpoint. Files are always linked to at least one other item. There are two types of links. The `file_item` and `file_itemtype` describe the item where the file originates from, for example a quotation or an import. If a file 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. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /contactpersons/{id}/files

Get Task collection -- With this endpoint, you can read, write, update and delete tasks. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /contactpersons/{id}/tasks

Get Contact collection -- Represents a company or a private person. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /contacts

Get Contact item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /contacts/{id}

Get ContactPerson collection -- Represents a person or department within a Contact. A Person item is always associated with one Contact. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /contacts/{id}/contactpersons

Get FileFolder collection -- 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. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /contacts/{id}/file_folders

Get File collection -- All user-generated documents and uploaded files are available in this endpoint. Files are always linked to at least one other item. There are two types of links. The `file_item` and `file_itemtype` describe the item where the file originates from, for example a quotation or an import. If a file 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. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /contacts/{id}/files

Get Task collection -- With this endpoint, you can read, write, update and delete tasks. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /contacts/{id}/tasks

Get Contract collection -- Represents contracts. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /contracts

Get Contract item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /contracts/{id}

Get File collection -- All user-generated documents and uploaded files are available in this endpoint. Files are always linked to at least one other item. There are two types of links. The `file_item` and `file_itemtype` describe the item where the file originates from, for example a quotation or an import. If a file 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. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /contracts/{id}/files

Get InvoiceLine collection -- Invoice lines are generated lines based on tax rates and ledgers of the items within an invoice. They sum up to the total of the invoice. Useful for exporting to accounting systems. It is currently not possible to get the exact same details which are displayed on the invoice pdf, since that depends on the used document template. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /contracts/{id}/invoicelines

Get Task collection -- With this endpoint, you can read, write, update and delete tasks. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /contracts/{id}/tasks

Get ProjectCost collection -- Represents additional costs in a project. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /costs

Get ProjectCost item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /costs/{id}

Get Crew collection -- With this endpoint you can retrieve crew members and their information. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /crew

Get Crew item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /crew/{id}

Get Appointment collection -- With this endpoint, you could read, write, update and delete appointments. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /crew/{id}/appointments

Get CrewAvailability collection -- Availability of the crew members. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /crew/{id}/crewavailability

Get CrewRates collection -- Represents the rates attached to crew members. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /crew/{id}/crewrates

Get FileFolder collection -- 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. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /crew/{id}/file_folders

Get File collection -- All user-generated documents and uploaded files are available in this endpoint. Files are always linked to at least one other item. There are two types of links. The `file_item` and `file_itemtype` describe the item where the file originates from, for example a quotation or an import. If a file 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. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /crew/{id}/files

Get Invitations collection -- With this endpoint, you can read sent invitations for crew functions. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /crew/{id}/invitations

Get Task collection -- With this endpoint, you can read, write, update and delete tasks. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /crew/{id}/tasks

Get CrewAvailability collection -- Availability of the crew members. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /crewavailability

Get CrewAvailability item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /crewavailability/{id}

Get CrewRates collection -- Represents the rates attached to crew members. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /crewrates

Get CrewRates item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /crewrates/{id}

Get Equipment collection -- All equipment. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /equipment

Get Equipment item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /equipment/{id}

Get Accessory collection -- Represents accessories of an equipment item. Each equipment can have multiple accessories. Accessories are equipment items themselves. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /equipment/{id}/accessories

Get Alternative collection -- Represents alternatives of an equipment item. Each equipment can have multiple alternatives. Alternatives are equipment items themselves. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /equipment/{id}/alternatives

Get EquipmentSetContent collection -- With this endpoint, you can retrieve the contents of combinations together with their information. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /equipment/{id}/equipmentsetscontent

Get FileFolder collection -- 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. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /equipment/{id}/file_folders

Get File collection -- All user-generated documents and uploaded files are available in this endpoint. Files are always linked to at least one other item. There are two types of links. The `file_item` and `file_itemtype` describe the item where the file originates from, for example a quotation or an import. If a file 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. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /equipment/{id}/files

Get Repair collection -- With this endpoint you can retrieve repairs and their information. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /equipment/{id}/repairs

Get SerialNumber collection -- Represents serial numbers, which are specific individual equipment pieces. This is a sub-item of Equipment and is always associated with a single Equipment item. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /equipment/{id}/serialnumbers

Get StockMovement collection -- Stock movements are all the changes that happen to the stock levels of an equipment. Those changes include manual changes, purchases, sales, transfers, stock corrections, repairs, marking lost or found, imports, stock counts. When creating or updating stock movements via the API only stock movements of type 'manual' are writable. Only stock movements for bulk items are available though the API. Stock movements for serialized equipment may be implemented at a later stage. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /equipment/{id}/stockmovements

Get Supplier collection -- Represents a supplier relationship between a contact and an equipment item. Each supplier entry links a contact to an equipment item, optionally with a purchase price and additional details. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /equipment/{id}/suppliers

Get Task collection -- With this endpoint, you can read, write, update and delete tasks. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /equipment/{id}/tasks

Get EquipmentAssignedSerials collection -- With this endpoint, you can retrieve the serial numbers assigned to serialized physical combinations together with their information. This endpoint only returns serials which have been assigned manually from the serial numbers tab, not actual content. Please see <a href="https://support.rentman.io/hc/en-us/articles/360018672100-How-to-add-serial-numbers-to-physical-combinations">this article</a> for more information. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /equipmentassignedserials

Get EquipmentAssignedSerials item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /equipmentassignedserials/{id}

Get EquipmentSetContent collection -- With this endpoint, you can retrieve the contents of combinations together with their information. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /equipmentsetscontent

Get EquipmentSetContent item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /equipmentsetscontent/{id}

Get ExtraInputField collection -- With this endpoint, you can read extra input fields. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /extrainputfields

Get ExtraInputField item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /extrainputfields/{id}

Get FactorGroups collection -- All factor groups. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /factorgroups

Get FactorGroups item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /factorgroups/{id}

Get Factors collection -- All factor. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /factorgroups/{id}/factors

Get Factors collection -- All factor. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /factors

Get Factors item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /factors/{id}

Get FileFolder collection -- 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. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /file_folders

Get FileFolder item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /file_folders/{id}

Get File collection -- All user-generated documents and uploaded files are available in this endpoint. Files are always linked to at least one other item. There are two types of links. The `file_item` and `file_itemtype` describe the item where the file originates from, for example a quotation or an import. If a file 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. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /files

Get File item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /files/{id}

Get Folder collection -- Contacts, equipment, crew, vehicles, containers, projecttemplates and default functions are organised into folders. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /folders

Get Folder item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /folders/{id}

Get Invitations collection -- With this endpoint, you can read sent invitations for crew functions. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /invitations

Get Invitations item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /invitations/{id}

Get InvoiceLine collection -- Invoice lines are generated lines based on tax rates and ledgers of the items within an invoice. They sum up to the total of the invoice. Useful for exporting to accounting systems. It is currently not possible to get the exact same details which are displayed on the invoice pdf, since that depends on the used document template. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /invoicelines

Get InvoiceLine item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /invoicelines/{id}

Get Factuur collection -- Represents invoices. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /invoices

Get Factuur item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /invoices/{id}

Get File collection -- All user-generated documents and uploaded files are available in this endpoint. Files are always linked to at least one other item. There are two types of links. The `file_item` and `file_itemtype` describe the item where the file originates from, for example a quotation or an import. If a file 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. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /invoices/{id}/files

Get InvoiceLine collection -- Invoice lines are generated lines based on tax rates and ledgers of the items within an invoice. They sum up to the total of the invoice. Useful for exporting to accounting systems. It is currently not possible to get the exact same details which are displayed on the invoice pdf, since that depends on the used document template. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /invoices/{id}/invoicelines

Get Payment collection -- Represents payments. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /invoices/{id}/payments

Get Task collection -- With this endpoint, you can read, write, update and delete tasks. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /invoices/{id}/tasks

Get LeaveMutations collection -- With this endpoint, you could work with leave mutations and their information. These items are immutable, so any mistakes made in the mutations should be corrected by creating a new (opposite) mutation. Duration is expressed in seconds. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /leavemutation

Get LeaveMutations item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /leavemutation/{id}

Get LeaveRequest collection -- With this endpoint, you could work with leave requests and their information. Make sure to also create the corresponding request lines for this request (by using the `/leaverequest/:id/timeregistration` endpoint). The leave type for the request lines must require approval (See `/leavetypes` endpoint for this information). Hours requests can be updated as long as they are in status 'Pending', once they get Approved/Rejected they can't be updated anymore besides transitioning a request from Approved to Cancelled. Once created, the crew member the request is for can't be updated. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /leaverequest

Get LeaveRequest item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /leaverequest/{id}

Get TimeRegistration collection -- With this endpoint, you could retrieve time registrations and their information. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /leaverequest/{id}/timeregistration

Get LeaveTypes collection -- With this endpoint, you could work with leave types and their information. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /leavetypes

Get LeaveTypes item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /leavetypes/{id}

Get Ledger collection -- Ledger codes are the codes defining the type of trade for an invoice line. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /ledgercodes

Get Ledger item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /ledgercodes/{id}

Get Payment collection -- Represents payments. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /payments

Get Payment item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /payments/{id}

Get ProjectCrew collection -- Represents the planning of crewmembers on Functions. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /projectcrew

Get ProjectCrew item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /projectcrew/{id}

Get ProjectEquipment collection -- Represents equipment items planned in a project. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /projectequipment

Get ProjectEquipment item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /projectequipment/{id}

Get ProjectEquipmentGroup collection -- Equipment groups of a project. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /projectequipmentgroup

Get ProjectEquipmentGroup item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /projectequipmentgroup/{id}

Get ProjectEquipment collection -- Represents equipment items planned in a project. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /projectequipmentgroup/{id}/projectequipment

Get ProjectFunctionGroup collection -- Function groups inside a project. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /projectfunctiongroups

Get ProjectFunctionGroup item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /projectfunctiongroups/{id}

Get ProjectFunction collection -- A function is a task that needs to be performed. Functions are connected to subprojects (and projects). Functions can be grouped inside function groups. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /projectfunctiongroups/{id}/projectfunctions

Get ProjectFunction collection -- A function is a task that needs to be performed. Functions are connected to subprojects (and projects). Functions can be grouped inside function groups. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /projectfunctions

Get ProjectFunction item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /projectfunctions/{id}

Get ProjectCrew collection -- Represents the planning of crewmembers on Functions. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /projectfunctions/{id}/projectcrew

Get ProjectVehicle collection -- Represents the vehicles planned for a function. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /projectfunctions/{id}/projectvehicles

Get ProjectRequestEquipment collection -- Project Request Equipment are equipment items linked to the Project Request. You can use this to add equipment items in a raw data format to the Project Request. The equipment items will be matched to the existing equipment items in the account when converting the Project Request into a Project in the Rentman interface. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /projectrequestequipment

Get ProjectRequestEquipment item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /projectrequestequipment/{id}

Get ProjectRequest collection -- Project Requests are incoming requests from external sources that allows you to turn into projects. These could come from another Rentman user, that is using the internal subrent request feature. By making also the POST endpoint available in the API, you can now also push these from other applications. For example from your CRM system, a form on your website, or any other source. The benefit of using Project Requests is that you can provide the data in a raw format. While converting a Project Request into a project from the Rentman interface, you can match this data to existing contacts, equipments etc. No need to set up complicated logic to fetch these items using the API first. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /projectrequests

Get ProjectRequest item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /projectrequests/{id}

Get ProjectRequestEquipment collection -- Project Request Equipment are equipment items linked to the Project Request. You can use this to add equipment items in a raw data format to the Project Request. The equipment items will be matched to the existing equipment items in the account when converting the Project Request into a Project in the Rentman interface. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /projectrequests/{id}/projectrequestequipment

Get Project collection -- Projects are the cornerstone of Rentman. Projects are connected to many other items. Projects always include one or more subprojects. When the user interface does not show any subprojects there is in fact a single one. See the /subprojects endpoint for more information. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /projects

Get Project item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /projects/{id}

Get Contract collection -- Represents contracts. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /projects/{id}/contracts

Get ProjectCost collection -- Represents additional costs in a project. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /projects/{id}/costs

Get FileFolder collection -- 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. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /projects/{id}/file_folders

Get File collection -- All user-generated documents and uploaded files are available in this endpoint. Files are always linked to at least one other item. There are two types of links. The `file_item` and `file_itemtype` describe the item where the file originates from, for example a quotation or an import. If a file 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. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /projects/{id}/files

Get ProjectCrew collection -- Represents the planning of crewmembers on Functions. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /projects/{id}/projectcrew

Get ProjectEquipment collection -- Represents equipment items planned in a project. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /projects/{id}/projectequipment

Get ProjectEquipmentGroup collection -- Equipment groups of a project. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /projects/{id}/projectequipmentgroup

Get ProjectFunctionGroup collection -- Function groups inside a project. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /projects/{id}/projectfunctiongroups

Get ProjectFunction collection -- A function is a task that needs to be performed. Functions are connected to subprojects (and projects). Functions can be grouped inside function groups. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /projects/{id}/projectfunctions

Get ProjectVehicle collection -- Represents the vehicles planned for a function. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /projects/{id}/projectvehicles

Get Quotation collection -- Represents quotes. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /projects/{id}/quotes

Get Subproject collection -- Subprojects are part of projects. All projects include at least one subproject. Information that differs from subproject to subproject, e.g. location, is retrieved in this endpoint. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /projects/{id}/subprojects

Get Task collection -- With this endpoint, you can read, write, update and delete tasks. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /projects/{id}/tasks

Get ProjectStatus collection -- Get project status objects. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /projectstatuses

Get ProjectStatus item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /projectstatuses/{id}

Get ProjectType collection -- Get a specific project type. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /projecttypes

Get ProjectType item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /projecttypes/{id}

Get ProjectVehicle collection -- Represents the vehicles planned for a function. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /projectvehicles

Get ProjectVehicle item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /projectvehicles/{id}

Get PurchaseOrderCost collection -- Represents line items within a purchase order. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /purchaseordercosts

Get PurchaseOrderCost item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /purchaseordercosts/{id}

Get PurchaseOrderGlobalCost collection -- Represents global costs of a purchase order. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /purchaseorderglobalcosts

Get PurchaseOrderGlobalCost item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /purchaseorderglobalcosts/{id}

Get PurchaseOrder collection -- Represents purchase orders. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /purchaseorders

Get PurchaseOrder item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /purchaseorders/{id}

Get FileFolder collection -- 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. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /purchaseorders/{id}/file_folders

Get File collection -- All user-generated documents and uploaded files are available in this endpoint. Files are always linked to at least one other item. There are two types of links. The `file_item` and `file_itemtype` describe the item where the file originates from, for example a quotation or an import. If a file 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. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /purchaseorders/{id}/files

Get InvoiceLine collection -- Invoice lines are generated lines based on tax rates and ledgers of the items within an invoice. They sum up to the total of the invoice. Useful for exporting to accounting systems. It is currently not possible to get the exact same details which are displayed on the invoice pdf, since that depends on the used document template. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /purchaseorders/{id}/invoicelines

Get PurchaseOrderCost collection -- Represents line items within a purchase order. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /purchaseorders/{id}/purchaseordercosts

Get PurchaseOrderGlobalCost collection -- Represents global costs of a purchase order. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /purchaseorders/{id}/purchaseorderglobalcosts

Get Task collection -- With this endpoint, you can read, write, update and delete tasks. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /purchaseorders/{id}/tasks

Get Quotation collection -- Represents quotes. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /quotes

Get Quotation item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /quotes/{id}

Get File collection -- All user-generated documents and uploaded files are available in this endpoint. Files are always linked to at least one other item. There are two types of links. The `file_item` and `file_itemtype` describe the item where the file originates from, for example a quotation or an import. If a file 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. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /quotes/{id}/files

Get InvoiceLine collection -- Invoice lines are generated lines based on tax rates and ledgers of the items within an invoice. They sum up to the total of the invoice. Useful for exporting to accounting systems. It is currently not possible to get the exact same details which are displayed on the invoice pdf, since that depends on the used document template. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /quotes/{id}/invoicelines

Get Task collection -- With this endpoint, you can read, write, update and delete tasks. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /quotes/{id}/tasks

Get CrewRateFactor collection -- Represents the rate factors for the crew rates. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /ratefactors

Get CrewRateFactor item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /ratefactors/{id}

Get CrewRate collection -- Represents crew rates. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /rates

Get CrewRate item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /rates/{id}

Get CrewRateFactor collection -- Represents the rate factors for the crew rates. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /rates/{id}/ratefactors

Get Repair collection -- With this endpoint you can retrieve repairs and their information. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /repairs

Get Repair item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /repairs/{id}

Get FileFolder collection -- 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. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /repairs/{id}/file_folders

Get File collection -- All user-generated documents and uploaded files are available in this endpoint. Files are always linked to at least one other item. There are two types of links. The `file_item` and `file_itemtype` describe the item where the file originates from, for example a quotation or an import. If a file 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. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /repairs/{id}/files

Get Task collection -- With this endpoint, you can read, write, update and delete tasks. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /repairs/{id}/tasks

Get SerialNumber collection -- Represents serial numbers, which are specific individual equipment pieces. This is a sub-item of Equipment and is always associated with a single Equipment item. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /serialnumbers

Get SerialNumber item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /serialnumbers/{id}

Get ActualContent collection -- Represents the actual content of serialized physical combinations. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /serialnumbers/{id}/actualcontent

Get EquipmentAssignedSerials collection -- With this endpoint, you can retrieve the serial numbers assigned to serialized physical combinations together with their information. This endpoint only returns serials which have been assigned manually from the serial numbers tab, not actual content. Please see <a href="https://support.rentman.io/hc/en-us/articles/360018672100-How-to-add-serial-numbers-to-physical-combinations">this article</a> for more information. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /serialnumbers/{id}/equipmentassignedserials

Get FileFolder collection -- 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. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /serialnumbers/{id}/file_folders

Get File collection -- All user-generated documents and uploaded files are available in this endpoint. Files are always linked to at least one other item. There are two types of links. The `file_item` and `file_itemtype` describe the item where the file originates from, for example a quotation or an import. If a file 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. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /serialnumbers/{id}/files

Get Task collection -- With this endpoint, you can read, write, update and delete tasks. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /serialnumbers/{id}/tasks

Get Status collection -- Get a status objects. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /statuses

Get Status item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /statuses/{id}

Get StockLocation collection -- With this endpoint, you can retrieve the stock locations and their information. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /stocklocations

Get StockLocation item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /stocklocations/{id}

Get Vehicle collection -- Represents vehicles. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /stocklocations/{id}/vehicles

Get StockMovement collection -- Stock movements are all the changes that happen to the stock levels of an equipment. Those changes include manual changes, purchases, sales, transfers, stock corrections, repairs, marking lost or found, imports, stock counts. When creating or updating stock movements via the API only stock movements of type 'manual' are writable. Only stock movements for bulk items are available though the API. Stock movements for serialized equipment may be implemented at a later stage. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /stockmovements

Get StockMovement item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /stockmovements/{id}

Get Subproject collection -- Subprojects are part of projects. All projects include at least one subproject. Information that differs from subproject to subproject, e.g. location, is retrieved in this endpoint. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /subprojects

Get Subproject item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /subprojects/{id}

Get FileFolder collection -- 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. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /subprojects/{id}/file_folders

Get ProjectCrew collection -- Represents the planning of crewmembers on Functions. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /subprojects/{id}/projectcrew

Get ProjectEquipment collection -- Represents equipment items planned in a project. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /subprojects/{id}/projectequipment

Get ProjectEquipmentGroup collection -- Equipment groups of a project. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /subprojects/{id}/projectequipmentgroup

Get ProjectFunctionGroup collection -- Function groups inside a project. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /subprojects/{id}/projectfunctiongroups

Get ProjectVehicle collection -- Represents the vehicles planned for a function. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /subprojects/{id}/projectvehicles

Get SubrentalEquipment collection -- With this endpoint you can retrieve information about subrental equipment. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /subrentalequipment

Get SubrentalEquipment item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /subrentalequipment/{id}

Get SubrentalEquipmentGroup collection -- With this endpoint you can retrieve information about subrental equipment groups. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /subrentalequipmentgroup

Get SubrentalEquipmentGroup item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /subrentalequipmentgroup/{id}

Get SubrentalEquipment collection -- With this endpoint you can retrieve information about subrental equipment. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /subrentalequipmentgroup/{id}/subrentalequipment

Get Subrental collection -- With this endpoint you can retrieve subrentals and their information. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /subrentals

Get Subrental item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /subrentals/{id}

Get FileFolder collection -- 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. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /subrentals/{id}/file_folders

Get File collection -- All user-generated documents and uploaded files are available in this endpoint. Files are always linked to at least one other item. There are two types of links. The `file_item` and `file_itemtype` describe the item where the file originates from, for example a quotation or an import. If a file 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. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /subrentals/{id}/files

Get SubrentalEquipment collection -- With this endpoint you can retrieve information about subrental equipment. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /subrentals/{id}/subrentalequipment

Get SubrentalEquipmentGroup collection -- With this endpoint you can retrieve information about subrental equipment groups. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /subrentals/{id}/subrentalequipmentgroup

Get Task collection -- With this endpoint, you can read, write, update and delete tasks. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /subrentals/{id}/tasks

Get Subtask collection -- With this endpoint, you can read, write, update and delete subtasks. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /subtasks

Get Subtask item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /subtasks/{id}

Get Supplier collection -- Represents a supplier relationship between a contact and an equipment item. Each supplier entry links a contact to an equipment item, optionally with a purchase price and additional details. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /suppliers

Get Supplier item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /suppliers/{id}

Get FileFolder collection -- 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. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /suppliers/{id}/file_folders

Get File collection -- All user-generated documents and uploaded files are available in this endpoint. Files are always linked to at least one other item. There are two types of links. The `file_item` and `file_itemtype` describe the item where the file originates from, for example a quotation or an import. If a file 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. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /suppliers/{id}/files

Get Task collection -- With this endpoint, you can read, write, update and delete tasks. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /suppliers/{id}/tasks

Get TaskAssignment collection -- With this endpoint, you can read, write, update and delete task assignments. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /taskassignments

Get TaskAssignment item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /taskassignments/{id}

Get Task collection -- With this endpoint, you can read, write, update and delete tasks. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /tasks

Get Task item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /tasks/{id}

Get FileFolder collection -- 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. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /tasks/{id}/file_folders

Get File collection -- All user-generated documents and uploaded files are available in this endpoint. Files are always linked to at least one other item. There are two types of links. The `file_item` and `file_itemtype` describe the item where the file originates from, for example a quotation or an import. If a file 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. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /tasks/{id}/files

Get Subtask collection -- With this endpoint, you can read, write, update and delete subtasks. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /tasks/{id}/subtasks

Get TaskAssignment collection -- With this endpoint, you can read, write, update and delete task assignments. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /tasks/{id}/taskassignments

Get TaskStatus collection -- With this endpoint, you can read, write, update and delete task statuses. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /taskstatuses

Get TaskStatus item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /taskstatuses/{id}

Get TaxClass collection -- Represents tax classes, which can be used to configure taxation rates. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /taxclasses

Get TaxClass item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /taxclasses/{id}

Get TimeRegistration collection -- With this endpoint, you could retrieve time registrations and their information. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /timeregistration

Get TimeRegistration item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /timeregistration/{id}

Get File collection -- All user-generated documents and uploaded files are available in this endpoint. Files are always linked to at least one other item. There are two types of links. The `file_item` and `file_itemtype` describe the item where the file originates from, for example a quotation or an import. If a file 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. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /timeregistration/{id}/files

Get TimeRegistrationActivity collection -- With this endpoint, you could retrieve the activities of the time registrations and their information. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /timeregistration/{id}/timeregistrationactivities

Get TimeRegistrationActivity collection -- With this endpoint, you could retrieve the activities of the time registrations and their information. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /timeregistrationactivities

Get TimeRegistrationActivity item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /timeregistrationactivities/{id}

Get Vehicle collection -- Represents vehicles. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /vehicles

Get Vehicle item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /vehicles/{id}

Get FileFolder collection -- 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. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /vehicles/{id}/file_folders

Get File collection -- All user-generated documents and uploaded files are available in this endpoint. Files are always linked to at least one other item. There are two types of links. The `file_item` and `file_itemtype` describe the item where the file originates from, for example a quotation or an import. If a file 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. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /vehicles/{id}/files

Get Task collection -- With this endpoint, you can read, write, update and delete tasks. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /vehicles/{id}/tasks

Get WarehouseStatus collection -- Get warehouse status objects. Collection response: `data` is an array, alongside `itemCount`, `limit`, `offset` and `next_page_url`. Page by sending the `cursor` value from `next_page_url` back as the `cursor` argument, not by incrementing `offset`; `next_page_url` is null on the last page. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /warehousestatuses

Get WarehouseStatus item. Single-item response: the item is under `data`. Linked fields are reference strings such as "/equipment/12" -- the shape this tool's output schema describes -- unless `expand` names them, which inlines the linked object instead and is NOT described by the output schema. via GET /warehousestatuses/{id}

Create Appointment item. The created or updated item is returned under `data`. via POST /appointments

Create AppointmentCrew item. The created or updated item is returned under `data`. via POST /appointments/{id}/appointmentcrew

Create Task item. The created or updated item is returned under `data`. via POST /contactpersons/{id}/tasks

Create Contact item. The created or updated item is returned under `data`. via POST /contacts

Create ContactPerson item. The created or updated item is returned under `data`. via POST /contacts/{id}/contactpersons

Create Task item. The created or updated item is returned under `data`. via POST /contacts/{id}/tasks

Create Task item. The created or updated item is returned under `data`. via POST /contracts/{id}/tasks

Create CrewAvailability item. The created or updated item is returned under `data`. via POST /crew/{id}/crewavailability

Create Task item. The created or updated item is returned under `data`. via POST /crew/{id}/tasks

Create Equipment item. The created or updated item is returned under `data`. via POST /equipment

Create Accessory item. The created or updated item is returned under `data`. via POST /equipment/{id}/accessories

Create Alternative item. The created or updated item is returned under `data`. via POST /equipment/{id}/alternatives

Create EquipmentSetContent item. The created or updated item is returned under `data`. via POST /equipment/{id}/equipmentsetscontent

Create SerialNumber item. The created or updated item is returned under `data`. via POST /equipment/{id}/serialnumbers

Create StockMovement item. The created or updated item is returned under `data`. via POST /equipment/{id}/stockmovements

Create Supplier item. The created or updated item is returned under `data`. via POST /equipment/{id}/suppliers

Create Task item. The created or updated item is returned under `data`. via POST /equipment/{id}/tasks

Create Folder item. The created or updated item is returned under `data`. via POST /folders

Create Payment item. The created or updated item is returned under `data`. via POST /invoices/{id}/payments

Create Task item. The created or updated item is returned under `data`. via POST /invoices/{id}/tasks

Create LeaveMutations item. The created or updated item is returned under `data`. via POST /leavemutation

Create LeaveRequest item. The created or updated item is returned under `data`. via POST /leaverequest

Create TimeRegistration item. The created or updated item is returned under `data`. via POST /leaverequest/{id}/timeregistration

Create ProjectRequest item. The created or updated item is returned under `data`. via POST /projectrequests

Create ProjectRequestEquipment item. The created or updated item is returned under `data`. via POST /projectrequests/{id}/projectrequestequipment

Create Project item. The created or updated item is returned under `data`. STABILITY: Rentman's API changelog reports the project creation and setup endpoints as BETA and subject to change; the pinned contract carries no per-operation marker, so treat the request and response shapes here as less settled than the rest of this provider. via POST /projects

Create ProjectCost item. The created or updated item is returned under `data`. STABILITY: Rentman's API changelog reports the project creation and setup endpoints as BETA and subject to change; the pinned contract carries no per-operation marker, so treat the request and response shapes here as less settled than the rest of this provider. via POST /projects/{id}/costs

Create ProjectFunctionGroup item. The created or updated item is returned under `data`. STABILITY: Rentman's API changelog reports the project creation and setup endpoints as BETA and subject to change; the pinned contract carries no per-operation marker, so treat the request and response shapes here as less settled than the rest of this provider. via POST /projects/{id}/projectfunctiongroups

Create ProjectFunction item. The created or updated item is returned under `data`. STABILITY: Rentman's API changelog reports the project creation and setup endpoints as BETA and subject to change; the pinned contract carries no per-operation marker, so treat the request and response shapes here as less settled than the rest of this provider. via POST /projects/{id}/projectfunctions

Create Subproject item. The created or updated item is returned under `data`. STABILITY: Rentman's API changelog reports the project creation and setup endpoints as BETA and subject to change; the pinned contract carries no per-operation marker, so treat the request and response shapes here as less settled than the rest of this provider. via POST /projects/{id}/subprojects

Create Task item. The created or updated item is returned under `data`. via POST /projects/{id}/tasks

Create Task item. The created or updated item is returned under `data`. via POST /purchaseorders/{id}/tasks

Create Task item. The created or updated item is returned under `data`. via POST /quotes/{id}/tasks

Create Task item. The created or updated item is returned under `data`. via POST /repairs/{id}/tasks

Create Task item. The created or updated item is returned under `data`. via POST /serialnumbers/{id}/tasks

Create Vehicle item. The created or updated item is returned under `data`. via POST /stocklocations/{id}/vehicles

Create Task item. The created or updated item is returned under `data`. via POST /subrentals/{id}/tasks

Create Task item. The created or updated item is returned under `data`. via POST /suppliers/{id}/tasks

Create Task item. The created or updated item is returned under `data`. via POST /tasks

Create Subtask item. The created or updated item is returned under `data`. via POST /tasks/{id}/subtasks

Create TaskAssignment item. The created or updated item is returned under `data`. via POST /tasks/{id}/taskassignments

Create TaskStatus item. The created or updated item is returned under `data`. via POST /taskstatuses

Create TimeRegistration item. The created or updated item is returned under `data`. via POST /timeregistration

Create Vehicle item. The created or updated item is returned under `data`. via POST /vehicles

Create Task item. The created or updated item is returned under `data`. via POST /vehicles/{id}/tasks

Update Accessory item. The created or updated item is returned under `data`. via PUT /accessories/{id}

Update Alternative item. The created or updated item is returned under `data`. via PUT /alternatives/{id}

Update AppointmentCrew item. The created or updated item is returned under `data`. via PUT /appointmentcrew/{id}

Update Appointment item. The created or updated item is returned under `data`. via PUT /appointments/{id}

Update ContactPerson item. The created or updated item is returned under `data`. via PUT /contactpersons/{id}

Update Contact item. The created or updated item is returned under `data`. via PUT /contacts/{id}

Update ProjectCost item. The created or updated item is returned under `data`. via PUT /costs/{id}

Update CrewAvailability item. The created or updated item is returned under `data`. via PUT /crewavailability/{id}

Update Equipment item. The created or updated item is returned under `data`. via PUT /equipment/{id}

Update EquipmentSetContent item. The created or updated item is returned under `data`. via PUT /equipmentsetscontent/{id}

Update Folder item. The created or updated item is returned under `data`. via PUT /folders/{id}

Update LeaveRequest item. The created or updated item is returned under `data`. via PUT /leaverequest/{id}

Update Payment item. The created or updated item is returned under `data`. via PUT /payments/{id}

Update ProjectRequestEquipment item. The created or updated item is returned under `data`. via PUT /projectrequestequipment/{id}

Update ProjectRequest item. The created or updated item is returned under `data`. via PUT /projectrequests/{id}

Update SerialNumber item. The created or updated item is returned under `data`. via PUT /serialnumbers/{id}

Update StockMovement item. The created or updated item is returned under `data`. via PUT /stockmovements/{id}

Update Subtask item. The created or updated item is returned under `data`. via PUT /subtasks/{id}

Update Supplier item. The created or updated item is returned under `data`. via PUT /suppliers/{id}

Update TaskAssignment item. The created or updated item is returned under `data`. via PUT /taskassignments/{id}

Update Task item. The created or updated item is returned under `data`. via PUT /tasks/{id}

Update TaskStatus item. The created or updated item is returned under `data`. via PUT /taskstatuses/{id}

Update TimeRegistration item. The created or updated item is returned under `data`. via PUT /timeregistration/{id}

Update Vehicle item. The created or updated item is returned under `data`. via PUT /vehicles/{id}