> **Building with AI coding agents?** Install the authstack plugin with one command. This equips your agent with accurate Scalekit implementation patterns.
>
> **Recommended** (the `-y` flags skip prompts, so the command runs without an interactive terminal):
> ```bash
> npx -y @scalekit-inc/cli setup -y
> ```
>
> Global:
> ```bash
> npm install -g @scalekit-inc/cli
> scalekit setup -y
> ```
>
> Supports Claude Code, Cursor, GitHub Copilot, Codex + skills for other Agent Skills-compatible agents in `~/.agents/skills`.
> Skills: integrate-agentkit, implement-saaskit, add-mcp-oauth, implement-sso, implement-scim.
> [Full setup guide](https://docs.scalekit.com/dev-kit/build-with-ai/)

---

# Connect AI agents to Rentman

The Rentman connector lets your AI agent act in each user's Rentman account. Each user connects their own Rentman access token once, and Scalekit sends it with every call, so your agent never handles credentials. It comes with 60 tools.

**Authentication:** Bearer Token
**Categories:** Project Management
**Tools:** 60: 36 read, 19 write, 5 destructive
**Users sign in with:** Access token
**Built by:** Scalekit connector
**Try it:** [Playground in the Scalekit dashboard](https://app.scalekit.com/ws/signup?sk_intent=playground&provider=RENTMAN)

## Setup

1. ### Install the SDK

   **Node.js**

   ```bash
   npm install @scalekit-sdk/node dotenv
   ```

   **Python**

   ```bash
   pip install scalekit-sdk-python python-dotenv
   ```

2. ### Set your credentials

   Add your Scalekit credentials to your `.env` file. Find values in **[app.scalekit.com](https://app.scalekit.com)** > **Developers** > **API Credentials**.

   ```sh title=".env"
   SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
   SCALEKIT_CLIENT_ID=<your-client-id>
   SCALEKIT_CLIENT_SECRET=<your-client-secret>
   ```

3. ### Create the Rentman connection

   In **AgentKit > Connections**, create a Rentman connection. The name you give it is the `connection_name` your code passes. See [Configure connections](/agentkit/connections/).

4. ### Authorize a user and make your first call

   **Node.js** (`quickstart.mts`)

   ```typescript
   import { ScalekitClient } from '@scalekit-sdk/node'
   import 'dotenv/config'
   import { createInterface } from 'node:readline/promises'

   const scalekit = new ScalekitClient(
     process.env.SCALEKIT_ENVIRONMENT_URL,
     process.env.SCALEKIT_CLIENT_ID,
     process.env.SCALEKIT_CLIENT_SECRET,
   )
   const actions = scalekit.actions

   const connector = 'rentman'
   const identifier = 'user_123'

   // Generate an authorization link for the user
   const { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })
   console.log('Authorize Rentman:', link)
   const rl = createInterface({ input: process.stdin, output: process.stdout })
   await rl.question('Press Enter after authorizing...')
   rl.close()

   // Make your first call
   const result = await actions.executeTool({
     connector,
     identifier,
     toolName: 'rentman_appointments_list',
     toolInput: {},
   })
   console.log(result)
   ```

   ```bash
   npx tsx quickstart.mts
   ```

   **Python** (`quickstart.py`)

   ```python
   import os
   from scalekit import ScalekitClient
   from dotenv import load_dotenv
   load_dotenv()

   scalekit_client = ScalekitClient(
       env_url=os.getenv("SCALEKIT_ENVIRONMENT_URL"),
       client_id=os.getenv("SCALEKIT_CLIENT_ID"),
       client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"),
   )
   actions = scalekit_client.actions

   connection_name = "rentman"
   identifier = "user_123"

   # Generate an authorization link for the user
   link_response = actions.get_authorization_link(
       connection_name=connection_name,
       identifier=identifier,
   )
   print("Authorize Rentman:", link_response.link)
   input("Press Enter after authorizing...")

   # Make your first call
   result = actions.execute_tool(
       tool_input={},
       tool_name="rentman_appointments_list",
       connection_name=connection_name,
       identifier=identifier,
   )
   print(result)
   ```

   ```bash
   python quickstart.py
   ```

   Each user opens the link once and enters their Rentman credentials there. See [Authorize a user](/agentkit/tools/authorize/) for the full flow and statuses.

## Tools

Pass the exact name to `execute_tool`, with an input like each tool's example. To ask for a tool that's missing, use the [request form](https://scalekitsupport.portal.usepylon.com/forms/request-a-connector-tool).

**Node.js**

```typescript
const result = await actions.executeTool({
  toolName: 'rentman_appointment_get',
  toolInput: {
    appointment_id: 4321,
  },
  connector: 'rentman',
  identifier: 'user_123',
})
```

**Python**

```python
result = actions.execute_tool(
    tool_name="rentman_appointment_get",
    tool_input={
        "appointment_id": 4321,
    },
    connection_name="rentman",
    identifier="user_123",
)
```

`result.data` is the app's response as JSON, and `result.execution_id` (`executionId` in Node.js) is the ID of the call.

### `rentman_appointment_get`

Get Appointment · Read-only

Get one appointment by ID.
Returns data with name, start, end, location, remark and crew.
Use rentman_appointment_get when you have the ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `appointment_id` (`integer`, required): Numeric ID of the appointment. Example: 4321.
- `expand` (`string`, optional): Comma-separated linked fields to inline as objects instead of paths, dot notation for nesting. Example: account_manager.
- `fields` (`string`, optional): Comma-separated fields to return (id, created and modified are always returned). Example: id,displayname,name.

Example input: `{"appointment_id":4321}`

### `rentman_appointments_list`

List Appointments · Read-only

List appointments (agenda items not tied to projects).
Returns data[] of appointments with name, start, end, location, remark and is_plannable, plus itemCount, limit and next_page_url.
Use rentman_appointments_list to read the agenda.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `cursor` (`string`, optional): Paging cursor taken from the cursor parameter of the previous response's next_page_url. Example: eyJhZnRlciI6NDU2LCJvcmRlciI6ImRlc2MiLCJsaW1pdCI6MTB9.
- `expand` (`string`, optional): Comma-separated linked fields to inline as objects instead of paths, dot notation for nesting. Example: account_manager.
- `fields` (`string`, optional): Comma-separated fields to return (id, created and modified are always returned). Example: id,displayname,name.
- `limit` (`integer`, optional): Items per page, up to 1500. Defaults to 300. Example: 100.
- `sort` (`string`, optional): Comma-separated fields to sort by, each prefixed with + (ascending) or - (descending). Example: -modified.

Example input: `{}`

### `rentman_contact_get`

Get Contact · Read-only

Get one contact by ID.
Returns data with name, type, code, addresses, emails, phones, VAT and discounts.
Use rentman_contact_get when you have the ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `contact_id` (`integer`, required): Numeric ID of the contact. Example: 4321.
- `expand` (`string`, optional): Comma-separated linked fields to inline as objects instead of paths, dot notation for nesting. Example: account_manager.
- `fields` (`string`, optional): Comma-separated fields to return (id, created and modified are always returned). Example: id,displayname,name.

Example input: `{"contact_id":4321}`

### `rentman_contact_person_get`

Get Contact Person · Read-only

Get one contact person by ID.
Returns data with name, function, contact, email and phones.
Use rentman_contact_person_get when you have the ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `contact_person_id` (`integer`, required): Numeric ID of the contact person. Example: 4321.
- `expand` (`string`, optional): Comma-separated linked fields to inline as objects instead of paths, dot notation for nesting. Example: account_manager.
- `fields` (`string`, optional): Comma-separated fields to return (id, created and modified are always returned). Example: id,displayname,name.

Example input: `{"contact_person_id":4321}`

### `rentman_contact_persons_list`

List Contact Persons · Read-only

List the contact persons of a contact.
Returns data[] of people with firstname, lastname, function, email, phone and mobilephone, plus itemCount, limit and next_page_url.
Use rentman_contact_persons_list for the people at a customer.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `contact_id` (`integer`, required): Numeric ID of the contact. Example: 4321.
- `cursor` (`string`, optional): Paging cursor taken from the cursor parameter of the previous response's next_page_url. Example: eyJhZnRlciI6NDU2LCJvcmRlciI6ImRlc2MiLCJsaW1pdCI6MTB9.
- `expand` (`string`, optional): Comma-separated linked fields to inline as objects instead of paths, dot notation for nesting. Example: account_manager.
- `fields` (`string`, optional): Comma-separated fields to return (id, created and modified are always returned). Example: id,displayname,name.
- `limit` (`integer`, optional): Items per page, up to 1500. Defaults to 300. Example: 100.
- `sort` (`string`, optional): Comma-separated fields to sort by, each prefixed with + (ascending) or - (descending). Example: -modified.

Example input: `{"contact_id":4321}`

### `rentman_contacts_list`

List Contacts · Read-only

List contacts (companies and private persons).
Returns data[] of contacts with id, displayname, type, code, email_1, phone_1 and addresses, plus itemCount, limit and next_page_url.
Use rentman_contacts_list to find a customer or supplier.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `cursor` (`string`, optional): Paging cursor taken from the cursor parameter of the previous response's next_page_url. Example: eyJhZnRlciI6NDU2LCJvcmRlciI6ImRlc2MiLCJsaW1pdCI6MTB9.
- `expand` (`string`, optional): Comma-separated linked fields to inline as objects instead of paths, dot notation for nesting. Example: account_manager.
- `fields` (`string`, optional): Comma-separated fields to return (id, created and modified are always returned). Example: id,displayname,name.
- `limit` (`integer`, optional): Items per page, up to 1500. Defaults to 300. Example: 100.
- `sort` (`string`, optional): Comma-separated fields to sort by, each prefixed with + (ascending) or - (descending). Example: -modified.

Example input: `{}`

### `rentman_crew_appointments_list`

List Crew Appointments · Read-only

List the appointments of a crew member.
Returns data[] of appointments with name, start, end, location and remark, plus itemCount, limit and next_page_url.
Use rentman_crew_appointments_list for a crew member's agenda.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `crew_id` (`integer`, required): Numeric ID of the crew member. Example: 4321.
- `cursor` (`string`, optional): Paging cursor taken from the cursor parameter of the previous response's next_page_url. Example: eyJhZnRlciI6NDU2LCJvcmRlciI6ImRlc2MiLCJsaW1pdCI6MTB9.
- `expand` (`string`, optional): Comma-separated linked fields to inline as objects instead of paths, dot notation for nesting. Example: account_manager.
- `fields` (`string`, optional): Comma-separated fields to return (id, created and modified are always returned). Example: id,displayname,name.
- `limit` (`integer`, optional): Items per page, up to 1500. Defaults to 300. Example: 100.
- `sort` (`string`, optional): Comma-separated fields to sort by, each prefixed with + (ascending) or - (descending). Example: -modified.

Example input: `{"crew_id":4321}`

### `rentman_crew_availability_list`

List Crew Availability · Read-only

List the availability entries of a crew member.
Returns data[] of availability with start, end, status and remark, plus itemCount, limit and next_page_url.
Use rentman_crew_availability_list before planning a crew member.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `crew_id` (`integer`, required): Numeric ID of the crew member. Example: 4321.
- `cursor` (`string`, optional): Paging cursor taken from the cursor parameter of the previous response's next_page_url. Example: eyJhZnRlciI6NDU2LCJvcmRlciI6ImRlc2MiLCJsaW1pdCI6MTB9.
- `expand` (`string`, optional): Comma-separated linked fields to inline as objects instead of paths, dot notation for nesting. Example: account_manager.
- `fields` (`string`, optional): Comma-separated fields to return (id, created and modified are always returned). Example: id,displayname,name.
- `limit` (`integer`, optional): Items per page, up to 1500. Defaults to 300. Example: 100.
- `sort` (`string`, optional): Comma-separated fields to sort by, each prefixed with + (ascending) or - (descending). Example: -modified.

Example input: `{"crew_id":4321}`

### `rentman_crew_list`

List Crew · Read-only

List crew members (employees and freelancers).
Returns data[] of crew with id, displayname, email, phone, function and active, plus itemCount, limit and next_page_url.
Use rentman_crew_list to find a crew member ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `cursor` (`string`, optional): Paging cursor taken from the cursor parameter of the previous response's next_page_url. Example: eyJhZnRlciI6NDU2LCJvcmRlciI6ImRlc2MiLCJsaW1pdCI6MTB9.
- `expand` (`string`, optional): Comma-separated linked fields to inline as objects instead of paths, dot notation for nesting. Example: account_manager.
- `fields` (`string`, optional): Comma-separated fields to return (id, created and modified are always returned). Example: id,displayname,name.
- `limit` (`integer`, optional): Items per page, up to 1500. Defaults to 300. Example: 100.
- `sort` (`string`, optional): Comma-separated fields to sort by, each prefixed with + (ascending) or - (descending). Example: -modified.

Example input: `{}`

### `rentman_crew_member_get`

Get Crew Member · Read-only

Get one crew member by ID.
Returns data with name, contact details, function, rates and active state.
Use rentman_crew_member_get when you have the ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `crew_id` (`integer`, required): Numeric ID of the crew member. Example: 4321.
- `expand` (`string`, optional): Comma-separated linked fields to inline as objects instead of paths, dot notation for nesting. Example: account_manager.
- `fields` (`string`, optional): Comma-separated fields to return (id, created and modified are always returned). Example: id,displayname,name.

Example input: `{"crew_id":4321}`

### `rentman_equipment_get`

Get Equipment · Read-only

Get one equipment item by ID.
Returns data with code, name, type, prices, stock quantities, dimensions and remarks.
Use rentman_equipment_get when you have the ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `equipment_id` (`integer`, required): Numeric ID of the equipment item. Example: 4321.
- `expand` (`string`, optional): Comma-separated linked fields to inline as objects instead of paths, dot notation for nesting. Example: account_manager.
- `fields` (`string`, optional): Comma-separated fields to return (id, created and modified are always returned). Example: id,displayname,name.

Example input: `{"equipment_id":4321}`

### `rentman_equipment_list`

List Equipment · Read-only

List equipment items, sets and cases in the inventory.
Returns data[] of equipment with id, code, name, type, rental_sales, price, current_quantity and folder, plus itemCount, limit and next_page_url.
Use rentman_equipment_list to find an equipment ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `cursor` (`string`, optional): Paging cursor taken from the cursor parameter of the previous response's next_page_url. Example: eyJhZnRlciI6NDU2LCJvcmRlciI6ImRlc2MiLCJsaW1pdCI6MTB9.
- `expand` (`string`, optional): Comma-separated linked fields to inline as objects instead of paths, dot notation for nesting. Example: account_manager.
- `fields` (`string`, optional): Comma-separated fields to return (id, created and modified are always returned). Example: id,displayname,name.
- `limit` (`integer`, optional): Items per page, up to 1500. Defaults to 300. Example: 100.
- `sort` (`string`, optional): Comma-separated fields to sort by, each prefixed with + (ascending) or - (descending). Example: -modified.

Example input: `{}`

### `rentman_equipment_serial_numbers_list`

List Equipment Serial Numbers · Read-only

List the serial-numbered units of an equipment item.
Returns data[] of serial numbers with serial, ref, active and purchase details, plus itemCount, limit and next_page_url.
Use rentman_equipment_serial_numbers_list to track individual units.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `equipment_id` (`integer`, required): Numeric ID of the equipment item. Example: 4321.
- `cursor` (`string`, optional): Paging cursor taken from the cursor parameter of the previous response's next_page_url. Example: eyJhZnRlciI6NDU2LCJvcmRlciI6ImRlc2MiLCJsaW1pdCI6MTB9.
- `expand` (`string`, optional): Comma-separated linked fields to inline as objects instead of paths, dot notation for nesting. Example: account_manager.
- `fields` (`string`, optional): Comma-separated fields to return (id, created and modified are always returned). Example: id,displayname,name.
- `limit` (`integer`, optional): Items per page, up to 1500. Defaults to 300. Example: 100.
- `sort` (`string`, optional): Comma-separated fields to sort by, each prefixed with + (ascending) or - (descending). Example: -modified.

Example input: `{"equipment_id":4321}`

### `rentman_equipment_stock_movements_list`

List Equipment Stock Movements · Read-only

List the stock movements of an equipment item.
Returns data[] of movements with amount, date, description, stock_location and projectequipment, plus itemCount, limit and next_page_url.
Use rentman_equipment_stock_movements_list for stock history.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `equipment_id` (`integer`, required): Numeric ID of the equipment item. Example: 4321.
- `cursor` (`string`, optional): Paging cursor taken from the cursor parameter of the previous response's next_page_url. Example: eyJhZnRlciI6NDU2LCJvcmRlciI6ImRlc2MiLCJsaW1pdCI6MTB9.
- `expand` (`string`, optional): Comma-separated linked fields to inline as objects instead of paths, dot notation for nesting. Example: account_manager.
- `fields` (`string`, optional): Comma-separated fields to return (id, created and modified are always returned). Example: id,displayname,name.
- `limit` (`integer`, optional): Items per page, up to 1500. Defaults to 300. Example: 100.
- `sort` (`string`, optional): Comma-separated fields to sort by, each prefixed with + (ascending) or - (descending). Example: -modified.

Example input: `{"equipment_id":4321}`

### `rentman_invoice_get`

Get Invoice · Read-only

Get one invoice by ID.
Returns data with number, project, customer, dates, totals and payment status.
Use rentman_invoice_get when you have the ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `invoice_id` (`integer`, required): Numeric ID of the invoice. Example: 4321.
- `expand` (`string`, optional): Comma-separated linked fields to inline as objects instead of paths, dot notation for nesting. Example: account_manager.
- `fields` (`string`, optional): Comma-separated fields to return (id, created and modified are always returned). Example: id,displayname,name.

Example input: `{"invoice_id":4321}`

### `rentman_invoice_lines_list`

List Invoice Lines · Read-only

List the lines of an invoice.
Returns data[] of lines with description, quantity, price and VAT, plus itemCount, limit and next_page_url.
Use rentman_invoice_lines_list for what was billed.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `invoice_id` (`integer`, required): Numeric ID of the invoice. Example: 4321.
- `cursor` (`string`, optional): Paging cursor taken from the cursor parameter of the previous response's next_page_url. Example: eyJhZnRlciI6NDU2LCJvcmRlciI6ImRlc2MiLCJsaW1pdCI6MTB9.
- `expand` (`string`, optional): Comma-separated linked fields to inline as objects instead of paths, dot notation for nesting. Example: account_manager.
- `fields` (`string`, optional): Comma-separated fields to return (id, created and modified are always returned). Example: id,displayname,name.
- `limit` (`integer`, optional): Items per page, up to 1500. Defaults to 300. Example: 100.
- `sort` (`string`, optional): Comma-separated fields to sort by, each prefixed with + (ascending) or - (descending). Example: -modified.

Example input: `{"invoice_id":4321}`

### `rentman_invoice_payments_list`

List Invoice Payments · Read-only

List the payments recorded on an invoice.
Returns data[] of payments with amount, date and description, plus itemCount, limit and next_page_url.
Use rentman_invoice_payments_list to check whether an invoice was paid.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `invoice_id` (`integer`, required): Numeric ID of the invoice. Example: 4321.
- `cursor` (`string`, optional): Paging cursor taken from the cursor parameter of the previous response's next_page_url. Example: eyJhZnRlciI6NDU2LCJvcmRlciI6ImRlc2MiLCJsaW1pdCI6MTB9.
- `expand` (`string`, optional): Comma-separated linked fields to inline as objects instead of paths, dot notation for nesting. Example: account_manager.
- `fields` (`string`, optional): Comma-separated fields to return (id, created and modified are always returned). Example: id,displayname,name.
- `limit` (`integer`, optional): Items per page, up to 1500. Defaults to 300. Example: 100.
- `sort` (`string`, optional): Comma-separated fields to sort by, each prefixed with + (ascending) or - (descending). Example: -modified.

Example input: `{"invoice_id":4321}`

### `rentman_invoices_list`

List Invoices · Read-only

List invoices.
Returns data[] of invoices with number, project, customer, date, expiration, price_invat and status, plus itemCount, limit and next_page_url.
Use rentman_invoices_list for billing overviews.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `cursor` (`string`, optional): Paging cursor taken from the cursor parameter of the previous response's next_page_url. Example: eyJhZnRlciI6NDU2LCJvcmRlciI6ImRlc2MiLCJsaW1pdCI6MTB9.
- `expand` (`string`, optional): Comma-separated linked fields to inline as objects instead of paths, dot notation for nesting. Example: account_manager.
- `fields` (`string`, optional): Comma-separated fields to return (id, created and modified are always returned). Example: id,displayname,name.
- `limit` (`integer`, optional): Items per page, up to 1500. Defaults to 300. Example: 100.
- `sort` (`string`, optional): Comma-separated fields to sort by, each prefixed with + (ascending) or - (descending). Example: -modified.

Example input: `{}`

### `rentman_project_contracts_list`

List Project Contracts · Read-only

List the contracts of a project.
Returns data[] of contracts with number, date and price, plus itemCount, limit and next_page_url.
Use rentman_project_contracts_list to see signed contracts.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `project_id` (`integer`, required): Numeric ID of the project. Example: 4321.
- `cursor` (`string`, optional): Paging cursor taken from the cursor parameter of the previous response's next_page_url. Example: eyJhZnRlciI6NDU2LCJvcmRlciI6ImRlc2MiLCJsaW1pdCI6MTB9.
- `expand` (`string`, optional): Comma-separated linked fields to inline as objects instead of paths, dot notation for nesting. Example: account_manager.
- `fields` (`string`, optional): Comma-separated fields to return (id, created and modified are always returned). Example: id,displayname,name.
- `limit` (`integer`, optional): Items per page, up to 1500. Defaults to 300. Example: 100.
- `sort` (`string`, optional): Comma-separated fields to sort by, each prefixed with + (ascending) or - (descending). Example: -modified.

Example input: `{"project_id":4321}`

### `rentman_project_costs_list`

List Project Costs · Read-only

List the additional costs on a project.
Returns data[] of costs with name, quantity, sale_price, purchase_price and subproject, plus itemCount, limit and next_page_url.
Use rentman_project_costs_list before adding one with rentman_project_cost_create.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `project_id` (`integer`, required): Numeric ID of the project. Example: 4321.
- `cursor` (`string`, optional): Paging cursor taken from the cursor parameter of the previous response's next_page_url. Example: eyJhZnRlciI6NDU2LCJvcmRlciI6ImRlc2MiLCJsaW1pdCI6MTB9.
- `expand` (`string`, optional): Comma-separated linked fields to inline as objects instead of paths, dot notation for nesting. Example: account_manager.
- `fields` (`string`, optional): Comma-separated fields to return (id, created and modified are always returned). Example: id,displayname,name.
- `limit` (`integer`, optional): Items per page, up to 1500. Defaults to 300. Example: 100.
- `sort` (`string`, optional): Comma-separated fields to sort by, each prefixed with + (ascending) or - (descending). Example: -modified.

Example input: `{"project_id":4321}`

### `rentman_project_crew_list`

List Project Crew · Read-only

List the crew planned on a project.
Returns data[] of crew plannings with crewmember, function, planperiod_start and planperiod_end, plus itemCount, limit and next_page_url.
Use rentman_project_crew_list to see who works on a project.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `project_id` (`integer`, required): Numeric ID of the project. Example: 4321.
- `cursor` (`string`, optional): Paging cursor taken from the cursor parameter of the previous response's next_page_url. Example: eyJhZnRlciI6NDU2LCJvcmRlciI6ImRlc2MiLCJsaW1pdCI6MTB9.
- `expand` (`string`, optional): Comma-separated linked fields to inline as objects instead of paths, dot notation for nesting. Example: account_manager.
- `fields` (`string`, optional): Comma-separated fields to return (id, created and modified are always returned). Example: id,displayname,name.
- `limit` (`integer`, optional): Items per page, up to 1500. Defaults to 300. Example: 100.
- `sort` (`string`, optional): Comma-separated fields to sort by, each prefixed with + (ascending) or - (descending). Example: -modified.

Example input: `{"project_id":4321}`

### `rentman_project_equipment_list`

List Project Equipment · Read-only

List the equipment planned on a project.
Returns data[] of planned equipment lines with equipment, quantity, planperiod, price and group, plus itemCount, limit and next_page_url.
Use rentman_project_equipment_list for a project's pick list.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `project_id` (`integer`, required): Numeric ID of the project. Example: 4321.
- `cursor` (`string`, optional): Paging cursor taken from the cursor parameter of the previous response's next_page_url. Example: eyJhZnRlciI6NDU2LCJvcmRlciI6ImRlc2MiLCJsaW1pdCI6MTB9.
- `expand` (`string`, optional): Comma-separated linked fields to inline as objects instead of paths, dot notation for nesting. Example: account_manager.
- `fields` (`string`, optional): Comma-separated fields to return (id, created and modified are always returned). Example: id,displayname,name.
- `limit` (`integer`, optional): Items per page, up to 1500. Defaults to 300. Example: 100.
- `sort` (`string`, optional): Comma-separated fields to sort by, each prefixed with + (ascending) or - (descending). Example: -modified.

Example input: `{"project_id":4321}`

### `rentman_project_get`

Get Project · Read-only

Get one project by ID.
Returns data with number, name, customer, location, account manager, dates, status and totals.
Use rentman_project_get for project details; use the rentman_project_*_list tools for its equipment, crew, costs and subprojects.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `project_id` (`integer`, required): Numeric ID of the project. Example: 4321.
- `expand` (`string`, optional): Comma-separated linked fields to inline as objects instead of paths, dot notation for nesting. Example: account_manager.
- `fields` (`string`, optional): Comma-separated fields to return (id, created and modified are always returned). Example: id,displayname,name.

Example input: `{"project_id":4321}`

### `rentman_project_quotes_list`

List Project Quotes · Read-only

List the quotes of a project.
Returns data[] of quotes with number, date, price and status, plus itemCount, limit and next_page_url.
Use rentman_project_quotes_list to find a quote, then rentman_quote_get.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `project_id` (`integer`, required): Numeric ID of the project. Example: 4321.
- `cursor` (`string`, optional): Paging cursor taken from the cursor parameter of the previous response's next_page_url. Example: eyJhZnRlciI6NDU2LCJvcmRlciI6ImRlc2MiLCJsaW1pdCI6MTB9.
- `expand` (`string`, optional): Comma-separated linked fields to inline as objects instead of paths, dot notation for nesting. Example: account_manager.
- `fields` (`string`, optional): Comma-separated fields to return (id, created and modified are always returned). Example: id,displayname,name.
- `limit` (`integer`, optional): Items per page, up to 1500. Defaults to 300. Example: 100.
- `sort` (`string`, optional): Comma-separated fields to sort by, each prefixed with + (ascending) or - (descending). Example: -modified.

Example input: `{"project_id":4321}`

### `rentman_project_statuses_list`

List Project Statuses · Read-only

List project statuses.
Returns data[] of statuses with id and name, plus itemCount, limit and next_page_url.
Use rentman_project_statuses_list to decode project status paths.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `cursor` (`string`, optional): Paging cursor taken from the cursor parameter of the previous response's next_page_url. Example: eyJhZnRlciI6NDU2LCJvcmRlciI6ImRlc2MiLCJsaW1pdCI6MTB9.
- `expand` (`string`, optional): Comma-separated linked fields to inline as objects instead of paths, dot notation for nesting. Example: account_manager.
- `fields` (`string`, optional): Comma-separated fields to return (id, created and modified are always returned). Example: id,displayname,name.
- `limit` (`integer`, optional): Items per page, up to 1500. Defaults to 300. Example: 100.
- `sort` (`string`, optional): Comma-separated fields to sort by, each prefixed with + (ascending) or - (descending). Example: -modified.

Example input: `{}`

### `rentman_project_subprojects_list`

List Project Subprojects · Read-only

List the subprojects of a project.
Returns data[] of subprojects with id, name, status, planperiod, location and totals, plus itemCount, limit and next_page_url.
Use rentman_project_subprojects_list to get subproject IDs and statuses.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `project_id` (`integer`, required): Numeric ID of the project. Example: 4321.
- `cursor` (`string`, optional): Paging cursor taken from the cursor parameter of the previous response's next_page_url. Example: eyJhZnRlciI6NDU2LCJvcmRlciI6ImRlc2MiLCJsaW1pdCI6MTB9.
- `expand` (`string`, optional): Comma-separated linked fields to inline as objects instead of paths, dot notation for nesting. Example: account_manager.
- `fields` (`string`, optional): Comma-separated fields to return (id, created and modified are always returned). Example: id,displayname,name.
- `limit` (`integer`, optional): Items per page, up to 1500. Defaults to 300. Example: 100.
- `sort` (`string`, optional): Comma-separated fields to sort by, each prefixed with + (ascending) or - (descending). Example: -modified.

Example input: `{"project_id":4321}`

### `rentman_project_vehicles_list`

List Project Vehicles · Read-only

List the vehicles planned on a project.
Returns data[] of vehicle plannings with vehicle, function and planperiod, plus itemCount, limit and next_page_url.
Use rentman_project_vehicles_list for transport planning.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `project_id` (`integer`, required): Numeric ID of the project. Example: 4321.
- `cursor` (`string`, optional): Paging cursor taken from the cursor parameter of the previous response's next_page_url. Example: eyJhZnRlciI6NDU2LCJvcmRlciI6ImRlc2MiLCJsaW1pdCI6MTB9.
- `expand` (`string`, optional): Comma-separated linked fields to inline as objects instead of paths, dot notation for nesting. Example: account_manager.
- `fields` (`string`, optional): Comma-separated fields to return (id, created and modified are always returned). Example: id,displayname,name.
- `limit` (`integer`, optional): Items per page, up to 1500. Defaults to 300. Example: 100.
- `sort` (`string`, optional): Comma-separated fields to sort by, each prefixed with + (ascending) or - (descending). Example: -modified.

Example input: `{"project_id":4321}`

### `rentman_projects_list`

List Projects · Read-only

List projects (each has one or more subprojects).
Returns data[] of projects with id, number, name, reference, customer, account_manager, planperiod and project_total_price, plus itemCount, limit and next_page_url.
Use rentman_projects_list to find a project ID. Filter with fields, sort and paging inputs.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `cursor` (`string`, optional): Paging cursor taken from the cursor parameter of the previous response's next_page_url. Example: eyJhZnRlciI6NDU2LCJvcmRlciI6ImRlc2MiLCJsaW1pdCI6MTB9.
- `expand` (`string`, optional): Comma-separated linked fields to inline as objects instead of paths, dot notation for nesting. Example: account_manager.
- `fields` (`string`, optional): Comma-separated fields to return (id, created and modified are always returned). Example: id,displayname,name.
- `limit` (`integer`, optional): Items per page, up to 1500. Defaults to 300. Example: 100.
- `sort` (`string`, optional): Comma-separated fields to sort by, each prefixed with + (ascending) or - (descending). Example: -modified.

Example input: `{}`

### `rentman_quote_get`

Get Quote · Read-only

Get one quote by ID.
Returns data with number, project, date, expiry, price and status.
Use rentman_quote_get after rentman_project_quotes_list.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `quote_id` (`integer`, required): Numeric ID of the quote. Example: 4321.
- `expand` (`string`, optional): Comma-separated linked fields to inline as objects instead of paths, dot notation for nesting. Example: account_manager.
- `fields` (`string`, optional): Comma-separated fields to return (id, created and modified are always returned). Example: id,displayname,name.

Example input: `{"quote_id":4321}`

### `rentman_repairs_list`

List Repairs · Read-only

List equipment repairs.
Returns data[] of repairs with equipment, serial number, reporter, dates, status and costs, plus itemCount, limit and next_page_url.
Use rentman_repairs_list to see which equipment is out for repair.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `cursor` (`string`, optional): Paging cursor taken from the cursor parameter of the previous response's next_page_url. Example: eyJhZnRlciI6NDU2LCJvcmRlciI6ImRlc2MiLCJsaW1pdCI6MTB9.
- `expand` (`string`, optional): Comma-separated linked fields to inline as objects instead of paths, dot notation for nesting. Example: account_manager.
- `fields` (`string`, optional): Comma-separated fields to return (id, created and modified are always returned). Example: id,displayname,name.
- `limit` (`integer`, optional): Items per page, up to 1500. Defaults to 300. Example: 100.
- `sort` (`string`, optional): Comma-separated fields to sort by, each prefixed with + (ascending) or - (descending). Example: -modified.

Example input: `{}`

### `rentman_statuses_list`

List Statuses · Read-only

List subproject statuses.
Returns data[] of statuses with id, name and color, plus itemCount, limit and next_page_url.
Use rentman_statuses_list to decode subproject status paths.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `cursor` (`string`, optional): Paging cursor taken from the cursor parameter of the previous response's next_page_url. Example: eyJhZnRlciI6NDU2LCJvcmRlciI6ImRlc2MiLCJsaW1pdCI6MTB9.
- `expand` (`string`, optional): Comma-separated linked fields to inline as objects instead of paths, dot notation for nesting. Example: account_manager.
- `fields` (`string`, optional): Comma-separated fields to return (id, created and modified are always returned). Example: id,displayname,name.
- `limit` (`integer`, optional): Items per page, up to 1500. Defaults to 300. Example: 100.
- `sort` (`string`, optional): Comma-separated fields to sort by, each prefixed with + (ascending) or - (descending). Example: -modified.

Example input: `{}`

### `rentman_subproject_get`

Get Subproject · Read-only

Get one subproject by ID.
Returns data with name, project, status, planperiod, location and totals.
Use rentman_subproject_get for one subproject.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `subproject_id` (`integer`, required): Numeric ID of the subproject. Example: 4321.
- `expand` (`string`, optional): Comma-separated linked fields to inline as objects instead of paths, dot notation for nesting. Example: account_manager.
- `fields` (`string`, optional): Comma-separated fields to return (id, created and modified are always returned). Example: id,displayname,name.

Example input: `{"subproject_id":4321}`

### `rentman_tasks_list`

List Tasks · Read-only

List tasks.
Returns data[] of tasks with name, details, priority, deadline, status, linked item and assignment, plus itemCount, limit and next_page_url.
Use rentman_tasks_list to see open to-dos.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `cursor` (`string`, optional): Paging cursor taken from the cursor parameter of the previous response's next_page_url. Example: eyJhZnRlciI6NDU2LCJvcmRlciI6ImRlc2MiLCJsaW1pdCI6MTB9.
- `expand` (`string`, optional): Comma-separated linked fields to inline as objects instead of paths, dot notation for nesting. Example: account_manager.
- `fields` (`string`, optional): Comma-separated fields to return (id, created and modified are always returned). Example: id,displayname,name.
- `limit` (`integer`, optional): Items per page, up to 1500. Defaults to 300. Example: 100.
- `sort` (`string`, optional): Comma-separated fields to sort by, each prefixed with + (ascending) or - (descending). Example: -modified.

Example input: `{}`

### `rentman_time_registration_get`

Get Time Registration · Read-only

Get one time registration by ID.
Returns data with crew member, start, end, durations and remark.
Use rentman_time_registration_get when you have the ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `time_registration_id` (`integer`, required): Numeric ID of the time registration. Example: 4321.
- `expand` (`string`, optional): Comma-separated linked fields to inline as objects instead of paths, dot notation for nesting. Example: account_manager.
- `fields` (`string`, optional): Comma-separated fields to return (id, created and modified are always returned). Example: id,displayname,name.

Example input: `{"time_registration_id":4321}`

### `rentman_time_registrations_list`

List Time Registrations · Read-only

List time registrations (worked hours and leave).
Returns data[] of registrations with crewmember, start, end, duration, break_duration, distance and remark, plus itemCount, limit and next_page_url.
Use rentman_time_registrations_list for timesheets.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `cursor` (`string`, optional): Paging cursor taken from the cursor parameter of the previous response's next_page_url. Example: eyJhZnRlciI6NDU2LCJvcmRlciI6ImRlc2MiLCJsaW1pdCI6MTB9.
- `expand` (`string`, optional): Comma-separated linked fields to inline as objects instead of paths, dot notation for nesting. Example: account_manager.
- `fields` (`string`, optional): Comma-separated fields to return (id, created and modified are always returned). Example: id,displayname,name.
- `limit` (`integer`, optional): Items per page, up to 1500. Defaults to 300. Example: 100.
- `sort` (`string`, optional): Comma-separated fields to sort by, each prefixed with + (ascending) or - (descending). Example: -modified.

Example input: `{}`

### `rentman_vehicles_list`

List Vehicles · Read-only

List vehicles.
Returns data[] of vehicles with name, license plate, seats and payload, plus itemCount, limit and next_page_url.
Use rentman_vehicles_list for transport resources.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `cursor` (`string`, optional): Paging cursor taken from the cursor parameter of the previous response's next_page_url. Example: eyJhZnRlciI6NDU2LCJvcmRlciI6ImRlc2MiLCJsaW1pdCI6MTB9.
- `expand` (`string`, optional): Comma-separated linked fields to inline as objects instead of paths, dot notation for nesting. Example: account_manager.
- `fields` (`string`, optional): Comma-separated fields to return (id, created and modified are always returned). Example: id,displayname,name.
- `limit` (`integer`, optional): Items per page, up to 1500. Defaults to 300. Example: 100.
- `sort` (`string`, optional): Comma-separated fields to sort by, each prefixed with + (ascending) or - (descending). Example: -modified.

Example input: `{}`

### `rentman_appointment_create`

Create Appointment · Write

Create an appointment in the agenda.
Returns data with the new appointment.
Use rentman_appointment_create for meetings, site visits or internal events.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `end` (`string`, required): End date-time (ISO 8601). Example: 2026-12-01T17:00:00+01:00.
- `start` (`string`, required): Start date-time (ISO 8601). Example: 2026-12-01T09:00:00+01:00.
- `color` (`string`, optional): Color as a hex code, for example #1171e4. Example: #1171e4.
- `is_plannable` (`boolean`, optional): If yes, employees can be scheduled during this appointment. Example: true.
- `is_public` (`boolean`, optional): Is Public. Example: true.
- `location` (`string`, optional): Location. Example: Main warehouse.
- `name` (`string`, optional): Name. Example: Site visit.
- `remark` (`string`, optional): Remark. Example: Bring the van keys.

Example input: `{"end":"<end>","start":"<start>"}`

### `rentman_appointment_update`

Update Appointment · Write

Update an appointment; only the fields you send change.
Returns data with the updated appointment.
Use rentman_appointment_update to move or rename an appointment.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `appointment_id` (`integer`, required): Numeric ID of the appointment. Example: 4321.
- `end` (`string`, required): End date-time (ISO 8601). Example: 2026-12-01T17:00:00+01:00.
- `start` (`string`, required): Start date-time (ISO 8601). Example: 2026-12-01T09:00:00+01:00.
- `color` (`string`, optional): Color as a hex code, for example #1171e4. Example: #1171e4.
- `is_plannable` (`boolean`, optional): If yes, employees can be scheduled during this appointment. Example: true.
- `is_public` (`boolean`, optional): Is Public. Example: true.
- `location` (`string`, optional): Location. Example: Main warehouse.
- `name` (`string`, optional): Name. Example: Site visit.
- `remark` (`string`, optional): Remark. Example: Bring the van keys.

Example input: `{"appointment_id":4321,"end":"<end>","start":"<start>"}`

### `rentman_contact_create`

Create Contact · Write

Create a contact: a company (set name) or a private person (set firstname and surname).
Returns data with the new contact.
Use rentman_contact_create for a new customer or supplier; add people with rentman_contact_person_create.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `accounting_code` (`string`, optional): External identifier used for integrations with accounting software. Example: DEB-1001.
- `code` (`string`, optional): Automatically generated if left empty. Example: C-1001.
- `country` (`string`, optional): Two-letter lowercase country code, for example nl. Example: nl.
- `custom` (`object`, optional): Custom field values keyed by the custom field name, for example {"custom_1": "VIP"}. Example: {"custom_1": "VIP"}
- `email_1` (`string`, optional): Email 1. Example: info@acme.example.
- `firstname` (`string`, optional): Firstname. Example: Anna.
- `folder` (`string`, optional): Folder as a path, for example /folders/3. Example: /folders/3.
- `invoice_city` (`string`, optional): Invoice City. Example: Amsterdam.
- `invoice_number` (`string`, optional): Invoice Number. Example: 1.
- `invoice_postalcode` (`string`, optional): Invoice Postalcode. Example: 1012 LG.
- `invoice_street` (`string`, optional): Invoice Street. Example: Damrak.
- `mailing_city` (`string`, optional): Mailing City. Example: Amsterdam.
- `mailing_number` (`string`, optional): Mailing Number. Example: 1.
- `mailing_postalcode` (`string`, optional): Mailing Postalcode. Example: 1012 LG.
- `mailing_street` (`string`, optional): Mailing Street. Example: Damrak.
- `name` (`string`, optional): Name. Example: Summer Festival 2026.
- `phone_1` (`string`, optional): Phone 1. Example: +31201234567.
- `surfix` (`string`, optional): Surfix. Example: van.
- `surname` (`string`, optional): Surname. Example: Jansen.
- `type` (`string`, optional): company or private. Example: company. One of: `private`, `company`.
- `vat_code` (`string`, optional): Vat Code. Example: NL123456789B01.
- `vendor_accounting_code` (`string`, optional): External identifier used for integrations with accounting software. Example: CRED-1001.
- `visit_city` (`string`, optional): Visit City. Example: Amsterdam.
- `visit_number` (`string`, optional): Visit Number. Example: 1.
- `visit_postalcode` (`string`, optional): Visit Postalcode. Example: 1012 LG.
- `visit_street` (`string`, optional): Visit Street. Example: Damrak.
- `website` (`string`, optional): Website. Example: https://acme.example.

Example input: `{}`

### `rentman_contact_person_create`

Create Contact Person · Write

Add a contact person to a contact.
Returns data with the new contact person.
Use rentman_contact_person_create after rentman_contact_create.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `contact_id` (`integer`, required): Numeric ID of the contact. Example: 4321.
- `city` (`string`, optional): City. Example: Amsterdam.
- `country` (`string`, optional): Two-letter lowercase country code, for example nl. Example: nl.
- `custom` (`object`, optional): Custom field values keyed by the custom field name, for example {"custom_1": "VIP"}. Example: {"custom_1": "VIP"}
- `email` (`string`, optional): Email. Example: anna@acme.example.
- `firstname` (`string`, optional): Firstname. Example: Anna.
- `function` (`string`, optional): Function. Example: Production manager.
- `lastname` (`string`, optional): Lastname. Example: Vries.
- `middle_name` (`string`, optional): Middle Name. Example: de.
- `mobilephone` (`string`, optional): Mobilephone. Example: +31612345678.
- `number` (`string`, optional): Number. Example: 2026-118.
- `phone` (`string`, optional): Phone. Example: +31201234567.
- `postalcode` (`string`, optional): Postalcode. Example: 1012 LG.
- `state` (`string`, optional): State. Example: Noord-Holland.
- `street` (`string`, optional): Street. Example: Damrak.

Example input: `{"contact_id":4321}`

### `rentman_contact_person_update`

Update Contact Person · Write

Update a contact person; only the fields you send change.
Returns data with the updated contact person.
Use rentman_contact_person_update to change a person's email, phone or function.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `contact_person_id` (`integer`, required): Numeric ID of the contact person. Example: 4321.
- `city` (`string`, optional): City. Example: Amsterdam.
- `country` (`string`, optional): Two-letter lowercase country code, for example nl. Example: nl.
- `custom` (`object`, optional): Custom field values keyed by the custom field name, for example {"custom_1": "VIP"}. Example: {"custom_1": "VIP"}
- `email` (`string`, optional): Email. Example: anna@acme.example.
- `firstname` (`string`, optional): Firstname. Example: Anna.
- `function` (`string`, optional): Function. Example: Production manager.
- `lastname` (`string`, optional): Lastname. Example: Vries.
- `middle_name` (`string`, optional): Middle Name. Example: de.
- `mobilephone` (`string`, optional): Mobilephone. Example: +31612345678.
- `number` (`string`, optional): Number. Example: 2026-118.
- `phone` (`string`, optional): Phone. Example: +31201234567.
- `postalcode` (`string`, optional): Postalcode. Example: 1012 LG.
- `state` (`string`, optional): State. Example: Noord-Holland.
- `street` (`string`, optional): Street. Example: Damrak.

Example input: `{"contact_person_id":4321}`

### `rentman_contact_update`

Update Contact · Write

Update a contact; only the fields you send change.
Returns data with the updated contact.
Use rentman_contact_update to change addresses, emails or codes.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `contact_id` (`integer`, required): Numeric ID of the contact. Example: 4321.
- `accounting_code` (`string`, optional): External identifier used for integrations with accounting software. Example: DEB-1001.
- `code` (`string`, optional): Automatically generated if left empty. Example: C-1001.
- `country` (`string`, optional): Two-letter lowercase country code, for example nl. Example: nl.
- `custom` (`object`, optional): Custom field values keyed by the custom field name, for example {"custom_1": "VIP"}. Example: {"custom_1": "VIP"}
- `email_1` (`string`, optional): Email 1. Example: info@acme.example.
- `firstname` (`string`, optional): Firstname. Example: Anna.
- `folder` (`string`, optional): Folder as a path, for example /folders/3. Example: /folders/3.
- `invoice_city` (`string`, optional): Invoice City. Example: Amsterdam.
- `invoice_number` (`string`, optional): Invoice Number. Example: 1.
- `invoice_postalcode` (`string`, optional): Invoice Postalcode. Example: 1012 LG.
- `invoice_street` (`string`, optional): Invoice Street. Example: Damrak.
- `mailing_city` (`string`, optional): Mailing City. Example: Amsterdam.
- `mailing_number` (`string`, optional): Mailing Number. Example: 1.
- `mailing_postalcode` (`string`, optional): Mailing Postalcode. Example: 1012 LG.
- `mailing_street` (`string`, optional): Mailing Street. Example: Damrak.
- `name` (`string`, optional): Name. Example: Summer Festival 2026.
- `phone_1` (`string`, optional): Phone 1. Example: +31201234567.
- `surfix` (`string`, optional): Surfix. Example: van.
- `surname` (`string`, optional): Surname. Example: Jansen.
- `type` (`string`, optional): company or private. Example: company. One of: `private`, `company`.
- `vat_code` (`string`, optional): Vat Code. Example: NL123456789B01.
- `vendor_accounting_code` (`string`, optional): External identifier used for integrations with accounting software. Example: CRED-1001.
- `visit_city` (`string`, optional): Visit City. Example: Amsterdam.
- `visit_number` (`string`, optional): Visit Number. Example: 1.
- `visit_postalcode` (`string`, optional): Visit Postalcode. Example: 1012 LG.
- `visit_street` (`string`, optional): Visit Street. Example: Damrak.
- `website` (`string`, optional): Website. Example: https://acme.example.

Example input: `{"contact_id":4321}`

### `rentman_equipment_create`

Create Equipment · Write

Create an equipment item, set or case in the inventory.
Returns data with the new equipment.
Use rentman_equipment_create to add a rental or sales item.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `code` (`string`, optional): Code. Example: C-1001.
- `custom` (`object`, optional): Custom field values keyed by the custom field name, for example {"custom_1": "VIP"}. Example: {"custom_1": "VIP"}
- `external_remark` (`string`, optional): Note on financial documents. Example: Includes power cable.
- `folder` (`string`, optional): Folder as a path, for example /folders/3. Example: /folders/3.
- `in_archive` (`boolean`, optional): In Archive. Example: true.
- `in_planner` (`boolean`, optional): In Planner. Example: true.
- `in_shop` (`boolean`, optional): In Shop. Example: true.
- `internal_remark` (`string`, optional): Note on packing lists. Example: Pack in flight case.
- `list_price` (`number`, optional): List Price. Example: 45.
- `name` (`string`, optional): Name. Example: Summer Festival 2026.
- `price` (`number`, optional): Price. Example: 45.
- `rental_sales` (`string`, optional): Rental Sales. Example: Rental. One of: `Sale`, `Rental`.
- `type` (`string`, optional): Type. Example: item. One of: `set`, `case`, `item`.
- `unit` (`string`, optional): Unit. Example: piece.
- `weight` (`number`, optional): Weight. Example: 12.5.

Example input: `{}`

### `rentman_equipment_stock_movement_create`

Create Stock Movement · Write

Record a stock change (added or removed units) for an equipment item.
Returns data with the new stock movement.
Use rentman_equipment_stock_movement_create to correct stock or book purchases and losses.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `date` (`string`, required): Date-time of the stock movement (ISO 8601). Example: 2026-12-01T09:00:00+01:00.
- `equipment_id` (`integer`, required): Numeric ID of the equipment item. Example: 4321.
- `amount` (`integer`, optional): Number of units moved; negative to remove stock. Example: 4.
- `description` (`string`, optional): Description. Example: Returned from repair.
- `details` (`string`, optional): Details. Example: Check all cables before loading.
- `stock_location` (`string`, optional): Stock location as a path, for example /stocklocations/1. Example: /stocklocations/1.

Example input: `{"date":"<date>","equipment_id":4321}`

### `rentman_equipment_update`

Update Equipment · Write

Update an equipment item; only the fields you send change.
Returns data with the updated equipment.
Use rentman_equipment_update to change a price, name, remark or archive an item.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `equipment_id` (`integer`, required): Numeric ID of the equipment item. Example: 4321.
- `code` (`string`, optional): Code. Example: C-1001.
- `custom` (`object`, optional): Custom field values keyed by the custom field name, for example {"custom_1": "VIP"}. Example: {"custom_1": "VIP"}
- `external_remark` (`string`, optional): Note on financial documents. Example: Includes power cable.
- `folder` (`string`, optional): Folder as a path, for example /folders/3. Example: /folders/3.
- `in_archive` (`boolean`, optional): In Archive. Example: true.
- `in_planner` (`boolean`, optional): In Planner. Example: true.
- `in_shop` (`boolean`, optional): In Shop. Example: true.
- `internal_remark` (`string`, optional): Note on packing lists. Example: Pack in flight case.
- `list_price` (`number`, optional): List Price. Example: 45.
- `name` (`string`, optional): Name. Example: Summer Festival 2026.
- `price` (`number`, optional): Price. Example: 45.
- `rental_sales` (`string`, optional): Rental Sales. Example: Rental. One of: `Sale`, `Rental`.
- `type` (`string`, optional): Type. Example: item. One of: `set`, `case`, `item`.
- `unit` (`string`, optional): Unit. Example: piece.
- `weight` (`number`, optional): Weight. Example: 12.5.

Example input: `{"equipment_id":4321}`

### `rentman_project_cost_create`

Create Project Cost · Write

Add an additional cost line to a project's subproject.
Returns data with the new cost.
Use rentman_project_cost_create for extra charges such as transport or catering.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `project_id` (`integer`, required): Numeric ID of the project. Example: 4321.
- `subproject` (`string`, required): Subproject the cost belongs to, as a path, for example /subprojects/55. Example: /subprojects/55.
- `custom` (`object`, optional): Custom field values keyed by the custom field name, for example {"custom_1": "VIP"}. Example: {"custom_1": "VIP"}
- `discount` (`number`, optional): Discount. Example: 0.
- `name` (`string`, optional): Name. Example: Summer Festival 2026.
- `purchase_price` (`number`, optional): Purchase Price. Example: 90.
- `quantity` (`integer`, optional): Quantity. Example: 2.
- `remark` (`string`, optional): Remark. Example: Bring the van keys.
- `sale_price` (`number`, optional): Sale Price. Example: 150.

Example input: `{"project_id":4321,"subproject":"<subproject>"}`

### `rentman_project_create`

Create Project · Write

Create a project.
Returns data with the new project.
Use rentman_project_create to start a new rental job; subprojects, equipment and crew are added in Rentman.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `account_manager` (`string`, optional): Account manager as a crew path, for example /crew/12. Example: /crew/12.
- `color` (`string`, optional): Color as a hex code, for example #1171e4. Example: #1171e4.
- `conditions` (`string`, optional): Conditions. Example: Payment within 14 days.
- `custom` (`object`, optional): Custom field values keyed by the custom field name, for example {"custom_1": "VIP"}. Example: {"custom_1": "VIP"}
- `deposit_status` (`string`, optional): Deposit Status. Example: no_deposit_paid. One of: `no_deposit_paid`, `deposit_paid`, `deposit_returned`.
- `name` (`string`, optional): Name. Example: Summer Festival 2026.
- `number` (`string`, optional): Number. Example: 2026-118.
- `reference` (`string`, optional): Reference. Example: PO-4471.

Example input: `{}`

### `rentman_project_update`

Update Project · Write

Update a project; only the fields you send change.
Returns data with the updated project.
Use rentman_project_update to rename a project or change its reference, color, conditions or custom fields.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `project_id` (`integer`, required): Numeric ID of the project. Example: 4321.
- `account_manager` (`string`, optional): Account manager as a crew path, for example /crew/12. Example: /crew/12.
- `color` (`string`, optional): Color as a hex code, for example #1171e4. Example: #1171e4.
- `conditions` (`string`, optional): Conditions. Example: Payment within 14 days.
- `custom` (`object`, optional): Custom field values keyed by the custom field name, for example {"custom_1": "VIP"}. Example: {"custom_1": "VIP"}
- `deposit_status` (`string`, optional): Deposit Status. Example: no_deposit_paid. One of: `no_deposit_paid`, `deposit_paid`, `deposit_returned`.
- `name` (`string`, optional): Name. Example: Summer Festival 2026.
- `number` (`string`, optional): Number. Example: 2026-118.
- `reference` (`string`, optional): Reference. Example: PO-4471.

Example input: `{"project_id":4321}`

### `rentman_subproject_planning_put_in`

Put Subproject in Planning · Write

Put a subproject in the planning so its equipment and crew are reserved.
Returns the updated subproject.
Use rentman_subproject_planning_put_in when a job is confirmed.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `subproject_id` (`integer`, required): Numeric ID of the subproject. Example: 4321.

Example input: `{"subproject_id":4321}`

### `rentman_subproject_planning_take_out`

Take Subproject out of Planning · Write

Take a subproject out of the planning, releasing its reservations.
Returns the updated subproject.
Use rentman_subproject_planning_take_out when a job is cancelled or on hold.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `subproject_id` (`integer`, required): Numeric ID of the subproject. Example: 4321.

Example input: `{"subproject_id":4321}`

### `rentman_subproject_update`

Update Subproject · Write

Rename a subproject or change its custom fields.
Returns data with the updated subproject.
Use rentman_subproject_update for subproject details.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `subproject_id` (`integer`, required): Numeric ID of the subproject. Example: 4321.
- `custom` (`object`, optional): Custom field values keyed by the custom field name, for example {"custom_1": "VIP"}. Example: {"custom_1": "VIP"}
- `name` (`string`, optional): Name. Example: Main stage.

Example input: `{"subproject_id":4321}`

### `rentman_task_create`

Create Task · Write

Create a task, optionally linked to a project, contact, equipment or other item.
Returns data with the new task.
Use rentman_task_create for follow-ups; color is required.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `color` (`string`, required): Color as a hex code, for example #1171e4. Example: #1171e4.
- `assignment_type` (`string`, optional): Assignment Type. Example: all_crewmembers. One of: `all_crewmembers`, `selected_crewmembers`, `creator_only`.
- `custom` (`object`, optional): Custom field values keyed by the custom field name, for example {"custom_1": "VIP"}. Example: {"custom_1": "VIP"}
- `deadline` (`string`, optional): Deadline. Example: 2026-12-01T12:00:00+01:00.
- `details` (`string`, optional): Details. Example: Check all cables before loading.
- `item` (`integer`, optional): Numeric ID of the item the task is linked to (plain integer, not a path). Example: 4321.
- `itemtype` (`string`, optional): Type of the linked item, for example Project, Contact or Equipment. Example: Project. One of: `Contact`, `Contract`, `DefaultService`, `SerialNumber`, `Factuur`, `Subrental`, `InventoryCountJob`, `InspectionReportSerialNumber`, `Supplier`, `Equipment`, `LostEquipment`, `Crew`, `Quotation`, `ContactPerson`, `Project`, `PurchaseOrder`, `Repair`, `Statistic`, `Vehicle`.
- `name` (`string`, optional): Name. Example: Summer Festival 2026.
- `priority` (`string`, optional): Priority. Example: medium_priority. One of: `no_priority`, `low_priority`, `medium_priority`, `high_priority`.
- `status` (`string`, optional): Task status as a path, for example /taskstatuses/1. Example: /taskstatuses/1.

Example input: `{"color":"<color>"}`

### `rentman_task_update`

Update Task · Write

Update a task; only the fields you send change.
Returns data with the updated task.
Use rentman_task_update to change status, deadline or priority.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `color` (`string`, required): Color as a hex code, for example #1171e4. Example: #1171e4.
- `task_id` (`integer`, required): Numeric ID of the task. Example: 4321.
- `assignment_type` (`string`, optional): Assignment Type. Example: all_crewmembers. One of: `all_crewmembers`, `selected_crewmembers`, `creator_only`.
- `custom` (`object`, optional): Custom field values keyed by the custom field name, for example {"custom_1": "VIP"}. Example: {"custom_1": "VIP"}
- `deadline` (`string`, optional): Deadline. Example: 2026-12-01T12:00:00+01:00.
- `details` (`string`, optional): Details. Example: Check all cables before loading.
- `item` (`integer`, optional): Numeric ID of the item the task is linked to (plain integer, not a path). Example: 4321.
- `itemtype` (`string`, optional): Type of the linked item, for example Project, Contact or Equipment. Example: Project. One of: `Contact`, `Contract`, `DefaultService`, `SerialNumber`, `Factuur`, `Subrental`, `InventoryCountJob`, `InspectionReportSerialNumber`, `Supplier`, `Equipment`, `LostEquipment`, `Crew`, `Quotation`, `ContactPerson`, `Project`, `PurchaseOrder`, `Repair`, `Statistic`, `Vehicle`.
- `name` (`string`, optional): Name. Example: Summer Festival 2026.
- `priority` (`string`, optional): Priority. Example: medium_priority. One of: `no_priority`, `low_priority`, `medium_priority`, `high_priority`.
- `status` (`string`, optional): Task status as a path, for example /taskstatuses/1. Example: /taskstatuses/1.

Example input: `{"color":"<color>","task_id":4321}`

### `rentman_time_registration_create`

Create Time Registration · Write

Register worked hours for a crew member.
Returns data with the new time registration.
Use rentman_time_registration_create to log hours.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `break_duration` (`number`, optional): Break length in seconds. Example: 1800.
- `crewmember` (`string`, optional): Crew member as a path, for example /crew/12. Example: /crew/12.
- `custom` (`object`, optional): Custom field values keyed by the custom field name, for example {"custom_1": "VIP"}. Example: {"custom_1": "VIP"}
- `distance` (`number`, optional): Distance. Example: 25.
- `duration` (`number`, optional): Duration in seconds; for worked hours it is calculated from start and end. Example: 28800.
- `end` (`string`, optional): End date-time (ISO 8601). Example: 2026-12-01T17:00:00+01:00.
- `is_lunch_included` (`boolean`, optional): Is Lunch Included. Example: false.
- `remark` (`string`, optional): Remark. Example: Bring the van keys.
- `start` (`string`, optional): Start date-time (ISO 8601). Example: 2026-12-01T09:00:00+01:00.
- `travel_time` (`number`, optional): Travel time in seconds. Example: 1800.

Example input: `{}`

### `rentman_time_registration_update`

Update Time Registration · Write

Update a time registration; only the fields you send change.
Returns data with the updated registration.
Use rentman_time_registration_update to correct hours.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `time_registration_id` (`integer`, required): Numeric ID of the time registration. Example: 4321.
- `break_duration` (`number`, optional): Break length in seconds. Example: 1800.
- `crewmember` (`string`, optional): Crew member as a path, for example /crew/12. Example: /crew/12.
- `custom` (`object`, optional): Custom field values keyed by the custom field name, for example {"custom_1": "VIP"}. Example: {"custom_1": "VIP"}
- `distance` (`number`, optional): Distance. Example: 25.
- `duration` (`number`, optional): Duration in seconds; for worked hours it is calculated from start and end. Example: 28800.
- `end` (`string`, optional): End date-time (ISO 8601). Example: 2026-12-01T17:00:00+01:00.
- `is_lunch_included` (`boolean`, optional): Is Lunch Included. Example: false.
- `remark` (`string`, optional): Remark. Example: Bring the van keys.
- `start` (`string`, optional): Start date-time (ISO 8601). Example: 2026-12-01T09:00:00+01:00.
- `travel_time` (`number`, optional): Travel time in seconds. Example: 1800.

Example input: `{"time_registration_id":4321}`

### `rentman_appointment_delete`

Delete Appointment · Destructive

Delete an appointment.
Returns no content on success.
Use rentman_appointment_delete to cancel an appointment.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `appointment_id` (`integer`, required): Numeric ID of the appointment. Example: 4321.

Example input: `{"appointment_id":4321}`

### `rentman_contact_delete`

Delete Contact · Destructive

Delete a contact.
Returns no content on success.
Use rentman_contact_delete only for contacts not used on projects.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `contact_id` (`integer`, required): Numeric ID of the contact. Example: 4321.

Example input: `{"contact_id":4321}`

### `rentman_contact_person_delete`

Delete Contact Person · Destructive

Delete a contact person.
Returns no content on success.
Use rentman_contact_person_delete to remove someone who left the company.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `contact_person_id` (`integer`, required): Numeric ID of the contact person. Example: 4321.

Example input: `{"contact_person_id":4321}`

### `rentman_task_delete`

Delete Task · Destructive

Delete a task.
Returns no content on success.
Use rentman_task_delete to remove a task.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `task_id` (`integer`, required): Numeric ID of the task. Example: 4321.

Example input: `{"task_id":4321}`

### `rentman_time_registration_delete`

Delete Time Registration · Destructive

Delete a time registration.
Returns no content on success.
Use rentman_time_registration_delete to remove a wrong entry.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `time_registration_id` (`integer`, required): Numeric ID of the time registration. Example: 4321.

Example input: `{"time_registration_id":4321}`

## Related

Other Project Management connectors ([all 67](/agentkit/connectors/?category=project-management)):

- [Notion](/agentkit/connectors/notion/): Scalekit connector, OAuth, 51 tools
- [Linear](/agentkit/connectors/linear/): Scalekit connector, OAuth, 64 tools
- [Airtable](/agentkit/connectors/airtable/): Scalekit connector, OAuth, 26 tools


---

## More Scalekit documentation

| Resource | What it contains | When to use it |
|----------|-----------------|----------------|
| [/llms.txt](/llms.txt) | Structured index with routing hints per product area | Start here — find which documentation set covers your topic before loading full content |
| [/llms-full.txt](/llms-full.txt) | Complete documentation for all Scalekit products in one file | Use when you need exhaustive context across multiple products or when the topic spans several areas |
| [sitemap-0.xml](https://docs.scalekit.com/sitemap-0.xml) | Full URL list of every documentation page | Use to discover specific page URLs you can fetch for targeted, page-level answers |
