[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# ResMan API and MCP server

> ResMan has an API, but only for approved Integration Partners (checked 23 Oct 2026). A property manager cannot get a key for their own account, and ResMan has no official MCP server. Partners get JSON endpoints for work orders, units, leases, prospects and ledgers.

Property management software for multifamily and affordable housing operators: leasing, accounting, maintenance and a resident portal on one platform, now branded ResMan by Inhabit.

## What is the ResMan API?

Cotlet's ResMan API exposes 13 endpoints for your own ResMan account: list properties, list units, list leases, list move-outs, list prospects, list work orders, get a work order, list work order categories and areas, list aged receivables, get a resident ledger, list vendors, create a work order and update a work order. The list_properties endpoint returns the properties your ResMan login can see. Each endpoint takes simple JSON inputs like property_id, status or modified_since and works both as an operation of the resman_read or resman_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Real estate](https://cotlet.dev/integrations/category/real-estate.md)
- **Endpoints:** 13 (11 read, 2 write)
- **Updated:** 2026-10-22

ResMan has an API, but only for approved Integration Partners (checked 23 Oct 2026). Cotlet is a hosted MCP server and REST API for ResMan with 13 endpoints (11 read, 2 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does ResMan have an official API?

ResMan has an API, but only for approved Integration Partners (checked 23 Oct 2026). A property manager cannot get a key for their own account, and ResMan has no official MCP server. Partners get JSON endpoints for work orders, units, leases, prospects and ledgers.

| Task | ResMan official | Cotlet |
|---|---|---|
| Read work orders | Partly: Partner API only | Yes |
| Create and update work orders | Partly: Partner API only | Yes |
| Unit status and availability | Partly: Partner API only | Yes |
| Leases and move-outs | Partly: Partner API only | Yes |
| Prospects and their status | Partly: Partner API only, read-only | Yes |
| Aged receivables and resident ledgers | Partly: Partner API only, read-only | Yes |
| Vendors | Partly: Partner API only | Yes |
| Use it with your own staff login, without applying as a partner | No | Yes |
| Run the standard reports as ResMan shows them | No | Yes |

Sources: [ResMan Partners API Documentation](https://partners-api-docs.myresman.com/), [ResMan Maintenance](https://www.myresman.com/solutions/maintenance/), [ResMan Reporting](https://www.myresman.com/solutions/reporting/), [ResMan Leasing](https://www.myresman.com/solutions/leasing/)

## Quick reference

```text
ResMan has an API, but only for approved Integration Partners (checked 23 Oct 2026). A property manager cannot get a key for their own account, and ResMan has no official MCP server. Partners get JSON endpoints for work orders, units, leases, prospects and ledgers.
Cotlet provides a hosted MCP server and REST API for ResMan: 13 tools (11 read, 2 write).
Access       Sign up at https://cotlet.dev/app/signup?app=resman, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    resman_read, resman_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/resman, each operation at its own route, e.g. POST /api/v1/resman/properties/{property_id}/work-orders
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in.
Operations   list_properties, list_units, list_leases, list_move_outs, list_prospects, list_work_orders, get_work_order, list_work_order_options, list_receivables, get_ledger, list_vendors, create_work_order, update_work_order
Confirm      create_work_order, update_work_order (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/resman-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=resman, requests ResMan in the Cotlet console and creates an API key there.
2. The user signs in to ResMan once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables ResMan for agents. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted ResMan server that someone else maintains, including non-developers.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Sign-in: the user signs in to ResMan in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get ResMan only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273).
API key: holds no ResMan login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once.
Terms: the user stays responsible for following ResMan's terms; Cotlet is not affiliated with ResMan.
```

## What can an AI agent do in ResMan?

Cotlet is best for property managers and operations teams on ResMan who want an AI agent to triage work orders, watch make-ready units and report receivables without running or fixing a server.

- **[Triage new maintenance work orders](https://cotlet.dev/integrations/resman-api-mcp-server/triage-new-work-orders.md)** (runs: daily): "List the new Submitted work orders at Lemon Tree. Set the priority by my rules (no heat, water leak, broken door lock = High), pick the category, assign each to a maintenance employee I name, and list the ones you are unsure about." → `list_work_orders`, `get_work_order`, `list_work_order_options`, `update_work_order`
- **[Track make-ready progress on vacant units](https://cotlet.dev/integrations/resman-api-mcp-server/track-make-ready-units.md)** (runs: daily): "List the units at Lemon Tree that are Not Ready and vacant. For each, check its make-ready work order and tell me which units are still open and when they are available to rent." → `list_units`, `list_work_orders`, `get_work_order`
- **[Summarize aged receivables](https://cotlet.dev/integrations/resman-api-mcp-server/aged-receivables-summary.md)** (runs: weekly): "For Lemon Tree, list every account with a balance over $500 today, largest first. For the top three, get the ledger since the first of the month and tell me what is unpaid." → `list_properties`, `list_receivables`, `get_ledger`
- **Weekly lease expiration and notice report** (runs: weekly): "For every property, list leases that end in the next 60 days and leases in Notice to Vacate, with the unit and end date. Add the move-outs of the last 30 days." → `list_properties`, `list_leases`, `list_move_outs`
- **Follow up with prospects who went quiet** (runs: daily): "List prospects at Lemon Tree whose status is still Prospect and who first contacted us in the last 14 days. Group them by source and tell me which ones have no leasing agent." → `list_prospects`
- **Create work orders from a walk-through list**: "From this walk-through list, create one work order per item at Lemon Tree, pick the category from ResMan's list and put each in the right unit." → `list_work_order_options`, `create_work_order`

## Can ResMan automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a ResMan connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to triage new maintenance work orders, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/resman/properties/{property_id}/work-orders. | Schedule Trigger node. |
| Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. |
| Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. |
| Your own script | GET https://cotlet.dev/api/v1/resman/properties/{property_id}/work-orders with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 13 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to ResMan.

### list_properties

The properties your ResMan login can see. Access: read. REST: `GET /api/v1/resman/properties`. MCP: `resman_read → list_properties`.

No parameters.

Returns each property with its id, name, type and city. Other tools take the property id.

Example response:

```json
{
  "properties": [
    {
      "property_id": "f308c33b-5865-4f7e-97af-46d35f19eddf",
      "name": "Lemon Tree",
      "type": "Multi-Family",
      "city": "Dallas",
      "state": "TX"
    }
  ]
}
```

### list_units

Units with status, vacancy status and date available. Access: read. REST: `GET /api/v1/resman/properties/{property_id}/units`. MCP: `resman_read → list_units`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `property_id` | string | yes | Property id from list_properties. |
| `status` | string | no | Not Ready, Ready, Down, Admin or Model. |
| `vacancy_status` | string | no | Occupied, Vacant, Notice to Vacate, Preleased, Vacant Preleased or Notice to Vacate Preleased. |

Returns the unit number, unit type, status and the date it changed, vacancy status, date available and market rent. The filters apply to the rows ResMan returns for the property. A unit with no available date returns null.

Example response:

```json
{
  "units": [
    {
      "unit_id": "fad50f9c-c20e-4d61-a8d0-4f54420d2cd0",
      "number": "1A",
      "unit_type": "A1",
      "status": "Not Ready",
      "status_date": "2026-10-14",
      "vacancy_status": "Vacant",
      "date_available": "2026-10-28",
      "market_rent": 1325
    },
    {
      "unit_id": "03047f59-50bc-41d1-8e48-669df3d8287e",
      "number": "2C",
      "unit_type": "B2",
      "status": "Not Ready",
      "status_date": "2026-10-19",
      "vacancy_status": "Vacant Preleased",
      "date_available": "2026-11-02",
      "market_rent": 1410
    }
  ]
}
```

### list_leases

Leases with status, dates, rent and residents. Access: read. REST: `GET /api/v1/resman/properties/{property_id}/leases`. MCP: `resman_read → list_leases`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `property_id` | string | yes | Property id from list_properties. |
| `status` | string | no | Pending, Pending Renewal, Pending Transfer, Denied, Cancelled, Current, Notice to Vacate, Month to Month, Under Eviction, Former, Evicted or Renewed. |
| `ends_before` | string | no | Only leases that end before this date, YYYY-MM-DD. |
| `modified_since` | string | no | Only leases changed since this date, YYYY-MM-DD. |

Returns one record per set of residents, with the lease in effect now: unit, status, start and end dates, rent and the main contacts. A set of residents that renewed shows its current lease, not each past one.

Example response:

```json
{
  "leases": [
    {
      "lease_id": "550c2838-1fe5-443f-b1f0-4306e341601d",
      "billing_account_id": "918f8290-5101-437f-8bd3-5cd846b6a964",
      "unit_number": "214",
      "status": "Notice to Vacate",
      "lease_start_date": "2025-12-01",
      "lease_end_date": "2026-11-30",
      "rent": 2150,
      "residents": [
        "Tomas Weber"
      ]
    }
  ]
}
```

### list_move_outs

Units vacated within a date range. Access: read. REST: `GET /api/v1/resman/properties/{property_id}/move-outs`. MCP: `resman_read → list_move_outs`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `property_id` | string | yes | Property id from list_properties. |
| `start_date` | string | yes | First day, YYYY-MM-DD. |
| `end_date` | string | yes | Last day, YYYY-MM-DD. |

Returns one row for each unit that was vacated in the range, with the last lease and the household. A resident who left while others stayed does not count, because only a vacated unit is a move-out.

Example response:

```json
{
  "move_outs": [
    {
      "unit_number": "13005",
      "unit_type": "A1",
      "lease_end_date": "2026-10-12",
      "lease_status": "Former",
      "prospect_source": "Apartment List",
      "residents": [
        "Elena Ruiz"
      ]
    }
  ]
}
```

### list_prospects

Prospects with status, source, first contact and leasing agent. Access: read. REST: `GET /api/v1/resman/properties/{property_id}/prospects`. MCP: `resman_read → list_prospects`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `property_id` | string | yes | Property id from list_properties. |
| `status` | string | no | Prospect, Applicant, Lost or Resident. |
| `first_contact_from` | string | no | Earliest first contact, YYYY-MM-DD. |
| `first_contact_to` | string | no | Latest first contact, YYYY-MM-DD. |
| `modified_since` | string | no | Only prospects changed since this time, YYYY-MM-DD. |

Returns the prospect source, status, first contact date and method, the assigned leasing agent and, for a lost prospect, the date and reason. ResMan refuses an unfiltered request, so give modified_since or a first contact range. A prospect stays in the Prospect status until an application is submitted.

Example response:

```json
{
  "prospects": [
    {
      "prospect_id": "9b8a224a-f260-4cc9-a05d-7098a4b08a29",
      "status": "Prospect",
      "prospect_source": "Property Website",
      "first_contact_date": "2026-10-14",
      "first_contact_method": "Phone",
      "leasing_agent": "Leslie Park",
      "lost_reason": null
    }
  ]
}
```

### list_work_orders

Work orders of a property, filtered by status, priority, location or assignee. Access: read. REST: `GET /api/v1/resman/properties/{property_id}/work-orders`. MCP: `resman_read → list_work_orders`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `property_id` | string | yes | Property id from list_properties. |
| `status` | string | no | Submitted, Not Started, In Progress, Completed, Scheduled, Cancelled, Closed or On Hold. |
| `priority` | string | no | Low, Medium or High. |
| `location` | string | no | Unit number, building name or rentable item name. |
| `assigned_to_person_id` | string | no | Person id of the assigned maintenance employee. |
| `modified_since` | string | no | Only work orders changed since this time, YYYY-MM-DD. |

Returns the number, status, priority, category, location, description, who reported it, the assignee and the due date, plus a make-ready flag. ResMan answers only when at least one filter is set besides the property.

Example response:

```json
{
  "work_orders": [
    {
      "work_order_id": "8e2474f7-9c89-4092-9316-31d4f234b8d6",
      "number": 1457,
      "status": "Submitted",
      "priority": "Medium",
      "category": "Heating",
      "location": {
        "name": "214",
        "type": "Unit"
      },
      "description": "No heat in the bedroom",
      "reported_by": "Tomas Weber",
      "assigned_to": null,
      "due_date": "2026-10-26",
      "is_make_ready": false
    }
  ]
}
```

### get_work_order

One work order in full, by its number. Access: read. REST: `GET /api/v1/resman/properties/{property_id}/work-order`. MCP: `resman_read → get_work_order`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `property_id` | string | yes | Property id from list_properties. |
| `number` | integer | yes | Work order number as shown in ResMan. |

Returns everything list_work_orders does plus the impacted areas, the pets, the appointment, the notes and the attached documents. Documents come as names and ids, not as images.

Example response:

```json
{
  "work_order_id": "8e2474f7-9c89-4092-9316-31d4f234b8d6",
  "number": 1457,
  "status": "Submitted",
  "priority": "Medium",
  "category": "Heating",
  "location": {
    "name": "214",
    "type": "Unit"
  },
  "areas": [
    "Bedroom 1"
  ],
  "pets": [
    "Cat"
  ],
  "appointment": "Permission Given",
  "description": "No heat in the bedroom",
  "notes": "Resident home after 5 pm",
  "reported_by": "Tomas Weber",
  "assigned_to": null,
  "documents": []
}
```

### list_work_order_options

The categories and areas your account uses on work orders. Access: read. REST: `GET /api/v1/resman/work-order-options`. MCP: `resman_read → list_work_order_options`.

No parameters.

Returns the work order categories with their ids and the list of areas. Both are defined by your account, so the names differ per company. create_work_order and update_work_order take the category id from here.

Example response:

```json
{
  "categories": [
    {
      "category_id": "1bb554a6-0b21-4690-83f2-b5650dadcf5e",
      "name": "Plumbing"
    },
    {
      "category_id": "22ae160b-a717-4c04-ad19-5f71280c23af",
      "name": "Carpet"
    }
  ],
  "areas": [
    "Bedroom 1",
    "Bathroom 1",
    "Kitchen",
    "Hallway"
  ]
}
```

### list_receivables

Outstanding balances per account on a date. Access: read. REST: `GET /api/v1/resman/properties/{property_id}/receivables`. MCP: `resman_read → list_receivables`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `property_id` | string | yes | Property id from list_properties. |
| `date` | string | yes | The date to read, YYYY-MM-DD. |
| `account_type` | string | no | Lease, Split Ledger, WOIT Account, Non-Resident Account or Prospect. |
| `min_balance` | number | no | Only accounts with a balance of at least this amount. |

Returns the accounts with outstanding charges, payments, credits and balance as of the date, largest balance first, plus the total of the rows returned. A balance below zero is an unapplied payment or credit. Transactions come from get_ledger.

Example response:

```json
{
  "property_id": "f308c33b-5865-4f7e-97af-46d35f19eddf",
  "date": "2026-10-23",
  "accounts": [
    {
      "billing_account_id": "b6d1a2c4-7e3f-4a98-9c10-5d2e8f3a1b47",
      "account_type": "Lease",
      "unit": "214",
      "account_name": "Tomas Weber",
      "charges": 2150,
      "payments": 300,
      "credits": 0,
      "balance": 1850
    },
    {
      "billing_account_id": "3904b2cd-1b5c-4efc-abc1-ca07f938ea9b",
      "account_type": "Lease",
      "unit": "102",
      "account_name": "Marissa Jackson",
      "charges": 1450,
      "payments": 0,
      "credits": 0,
      "balance": 1450
    },
    {
      "billing_account_id": "c8e4f1a9-2b6d-4d37-8a05-9e7b3c2d4f61",
      "account_type": "Lease",
      "unit": "305",
      "account_name": "Priya Nair",
      "charges": 760,
      "payments": 0,
      "credits": 0,
      "balance": 760
    }
  ],
  "total_balance": 4060
}
```

### get_ledger

The transactions on one billing account. Access: read. REST: `GET /api/v1/resman/properties/{property_id}/ledger`. MCP: `resman_read → get_ledger`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `property_id` | string | yes | Property id from list_properties. |
| `billing_account_id` | string | yes | Billing account id from list_receivables or list_leases. |
| `posted_since` | string | no | Only transactions posted on or after this date, YYYY-MM-DD. |

Returns each transaction with its date, type (Charge, Credit or Payment), category and amount, oldest first. It reads the ledger and posts nothing.

Example response:

```json
{
  "billing_account_id": "b6d1a2c4-7e3f-4a98-9c10-5d2e8f3a1b47",
  "transactions": [
    {
      "date": "2026-10-01",
      "type": "Charge",
      "category": "Rent",
      "amount": 2150
    },
    {
      "date": "2026-10-09",
      "type": "Payment",
      "category": "Payment",
      "amount": 300
    }
  ]
}
```

### list_vendors

Vendors whose company name starts with the text you give. Access: read. REST: `GET /api/v1/resman/vendors`. MCP: `resman_read → list_vendors`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `company` | string | yes | Start of the vendor company name. |

Returns the vendor id, company, abbreviation, whether it is approved, the contact and the phone number. The match is on the start of the name, so "Classic" finds "Classic Tile".

Example response:

```json
{
  "vendors": [
    {
      "vendor_id": "9ff22dfc-e1b7-4ee9-a9eb-902ef70b5776",
      "company": "Classic Tile",
      "abbreviation": "CT",
      "is_approved": true,
      "contact": "Classic Tile",
      "phone": "800-123-4576"
    }
  ]
}
```

### create_work_order

Adds a new work order at a unit, building or rentable item. Access: write, asks the user first. REST: `POST /api/v1/resman/properties/{property_id}/work-orders`. MCP: `resman_write → create_work_order`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `property_id` | string | yes | Property id from list_properties. |
| `description` | string | yes | What is wrong, up to 248 characters. |
| `category_id` | string | yes | Category id from list_work_order_options. |
| `location_type` | string | yes | Unit, Building, Rentable Item or WOIT Account. |
| `location` | string | yes | Unit number, building name or the id of the location. |
| `reported_by` | string | no | Name of the resident who reported it. |
| `assigned_to_person_id` | string | no | Person id of a maintenance employee. |
| `priority` | string | no | Low, Medium or High. |
| `areas` | array | no | Impacted areas from list_work_order_options. |
| `notes` | string | no | Longer notes for the technician. |

Returns the new work order id and its number. The work order shows in ResMan at once, and a resident who reported it can follow its progress. ResMan sets the due date from your account settings when you give none. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "work_order_id": "a68ce6b2-a9ef-4127-bf97-067e9f4a548c",
  "number": 1009,
  "property_id": "f308c33b-5865-4f7e-97af-46d35f19eddf"
}
```

### update_work_order

Changes the status, priority, category, assignee or dates of a work order. Access: write, asks the user first. REST: `PATCH /api/v1/resman/properties/{property_id}/work-orders/{work_order_id}`. MCP: `resman_write → update_work_order`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `property_id` | string | yes | Property id from list_properties. |
| `work_order_id` | string | yes | Work order id from list_work_orders. |
| `status` | string | no | Submitted, Not Started, In Progress, Completed, Scheduled, Cancelled, Closed or On Hold. |
| `priority` | string | no | Low, Medium or High. |
| `category_id` | string | no | Category id from list_work_order_options. |
| `assigned_to_person_id` | string | no | Person id of a maintenance employee. |
| `scheduled_date` | string | no | When the work is scheduled, YYYY-MM-DD HH:MM in the property time. |
| `notes` | string | no | Notes for the technician. |

Returns the work order as saved. A status change is visible to the resident who reported it. ResMan accepts only an employee marked as a maintenance employee as the assignee and refuses any other. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "work_order_id": "a68ce6b2-a9ef-4127-bf97-067e9f4a548c",
  "property_id": "f308c33b-5865-4f7e-97af-46d35f19eddf",
  "status": "Not Started",
  "priority": "High",
  "assigned_to": "Robert Wilcox"
}
```

## How do I connect ResMan to Claude Code, Codex or Cursor?

Connecting ResMan takes three steps: sign up, sign in to ResMan once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key.

### Connect ResMan to your agent.

1. **Create an account** Sign up and add ResMan in the console. Your API key is there too.

2. **Sign in to ResMan in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to ResMan there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   Claude Code:

```
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

   Cursor:

```
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

   Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

4. **Ask your agent** Ask in plain words. Your agent finds the ResMan tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
List the new Submitted work orders at Lemon Tree. Set the priority by my rules (no heat, water leak, broken door lock = High), pick the category, assign each to a maintenance employee I name, and list the ones you are unsure about.
```

### Call ResMan from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is an endpoint under /api/v1/resman with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise.

```
curl -X POST https://cotlet.dev/api/v1/resman/properties/f308c33b-5865-4f7e-97af-46d35f19eddf/work-orders \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"description":"Kitchen faucet leaks under the sink","category_id":"1bb554a6-0b21-4690-83f2-b5650dadcf5e","location_type":"Unit","location":"201","reported_by":"Dana Whitfield","priority":"Medium"}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "work_order_id": "a68ce6b2-a9ef-4127-bf97-067e9f4a548c",
  "number": 1009,
  "property_id": "f308c33b-5865-4f7e-97af-46d35f19eddf"
}
```

## Why use Cotlet for ResMan?

**Built for agents**

- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.

**Your login stays yours**

- You sign in to ResMan yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses.
- A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Scope each API key: its apps, its tools, read only or read and write.
- Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you.
- Every background request listed in your Background activity. Disable for agents in one click.

**Kept working for you**

- We test every integration every 6 hours.
- When ResMan changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect ResMan to Cotlet?

Yes. You sign in to ResMan yourself, in your own Cloud Browser, and we never save your password. Your agents only get ResMan once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself.

- **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev)
- **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on)
- **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev)
- **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev)

[How Cotlet protects your access](https://cotlet.dev/security.md)

### Common concerns

**Who runs Cotlet?**

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

**Is this an official ResMan integration?**

No, Cotlet is independent of ResMan. ResMan's own API is open only to approved partners. Cotlet works through your own ResMan account, the way you use ResMan in the browser, so you need no partner approval and no developer setup.

**What about client data and GDPR?**

Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it.

**Can I start with read only?**

Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool.

**Is it reliable?**

Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev.

**How do I stop?**

Press Disable for agents next to ResMan in your console: your agents lose access at once and you stay signed in. Signing out of ResMan in the browser works too, and Reset browser deletes the whole profile.

## Is there a ResMan MCP server on GitHub?

No community ResMan MCP server exists on GitHub. The official route is the Partner API: your company applies as an Integration Partner, gets an Integration Partner Id and API key, and sends each client's account id with every request. It is built for software vendors, so a property manager usually cannot use it. Cotlet works in your own ResMan login and hosts the MCP server and REST API for you.

|  | Partner API | Cotlet |
|---|---|---|
| Setup | Apply as an Integration Partner, wait for approval, then build and host your own integration | Sign up, sign in to ResMan once, add one MCP server or API key |
| When ResMan changes | ResMan versions the API; you update your code | Our team tests it daily and fixes it for you; failed calls are free |
| Your ResMan access | Integration Partner Id and API key, plus the account id of each client | Your own Cloud Browser in the EU with your session, profile encrypted, only for the apps you enable, disabled for agents in one click |
| When access ends | A missing or invalid key gets a 401 response | If ResMan logs you out, your agent gets a link to sign in again |
| Upkeep | You host, monitor and update the integration | Nothing to host or update |
| Where it runs | Wherever you deploy it | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Not listed in the API docs | Free 7-day trial, then pay-as-you-go credit packs, no subscription |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when ResMan changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want your sign-in to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the ResMan API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the ResMan API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 10 credits (about $0.04 to $0.06), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over.

| Credits | Price, one time | Calls at 10 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 500 | $5.80 |
| 15,000 | $79 | 1,500 | $5.27 |
| 32,000 | $149 | 3,200 | $4.66 |
| 60,000 | $249 | 6,000 | $4.15 |

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing.md)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own ResMan account.

- **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms)
- **Your sign-in:** You sign in to ResMan yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get ResMan only after you enable it. When ResMan signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md)
- **Revoking access:** Press Disable for agents next to ResMan, sign out of ResMan in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **ResMan's terms:** You use your own ResMan account and stay responsible for following ResMan's terms. Cotlet is independent and not affiliated with ResMan. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Sign up free, open ResMan in the console and press Request access. Then you create your API key and connect ResMan there.

**Do I need to be technical?**

No. You sign in to ResMan once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is it safe to connect ResMan to Cotlet?**

Yes. You sign in to ResMan yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get ResMan once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

**Is a hosted server safer than a local one? My ResMan sign-in would leave my computer.**

On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your ResMan cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off.

**Why does Cotlet send requests instead of clicking in my browser?**

To be fast, Cotlet doesn't click through ResMan's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. ResMan sees the same browser and IP you signed in with, and every request is listed in your Background activity.

**What if someone gets my Cotlet API key?**

The key holds no ResMan login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once.

**Why a signed-in browser and not OAuth, like other integration platforms?**

ResMan offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273).

**Can my agent post charges, take payments or pay invoices in ResMan?**

No. The ResMan tools read ledgers, receivables, leases and prospects, and write only work orders. Posting charges, taking payments and paying invoices stay in ResMan, even though the Partner API documents an invoice payment method.

**Which work order statuses can my agent set?**

update_work_order sets Submitted, Not Started, In Progress, Completed, Scheduled, Cancelled, Closed or On Hold, the statuses ResMan documents for work orders. A resident who reported the work order can see the new status in the Resident Portal, so each update asks for your OK by default.

**Can my agent post or send messages in ResMan without asking me?**

No. Every call to create_work_order or update_work_order waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals.

**Can I use the ResMan API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/resman from the HTTP Request node.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.