DoorLoop API and MCP server

• POST

  list_properties

  Your properties with address, type and unit count.

  read

  Returns the properties in your DoorLoop account, with address and number of units. Search matches the property name or address. Use the property_id of each item in the other tools.

  POST /api/v1/doorloop/list_properties

  Input

  Input: list_properties

  Parameter	Type	Description
  search	string	Match on property name or address.
  cursor	string	Next page cursor from the previous call.

  Example response

  {
    "properties": [
      {
        "property_id": "pr_3a91c7",
        "name": "Maple Court",
        "address": "120 Maple St, Springfield",
        "type": "Multi-family",
        "units": 12
      }
    ],
    "next_cursor": null
  }

• POST

  list_units

  Units with property, rent and whether each is occupied or vacant.

  read

  Returns units with the property they belong to and their occupancy. Filter by property or by occupied or vacant. Use unit_id from here in create_lease.

  POST /api/v1/doorloop/list_units

  Input

  Input: list_units

  Parameter	Type	Description
  property_id	string	Only this property. Property ID from list_properties.
  status	enum	all, occupied or vacant. Default: all.
  cursor	string	Next page cursor from the previous call.

  Example response

  {
    "units": [
      {
        "unit_id": "un_5b20d4",
        "property": "Maple Court",
        "name": "Unit 4",
        "status": "vacant",
        "market_rent": "1600.00"
      }
    ],
    "next_cursor": null
  }

• POST

  list_tenants

  Tenants with email, phone, unit and current lease.

  read

  Returns tenants with contact details and the lease they are on. Search matches name, email or phone. Use tenant_id from here in create_lease.

  POST /api/v1/doorloop/list_tenants

  Input

  Input: list_tenants

  Parameter	Type	Description
  search	string	Match on name, email or phone.
  property_id	string	Only this property. Property ID from list_properties.
  cursor	string	Next page cursor from the previous call.

  Example response

  {
    "tenants": [
      {
        "tenant_id": "tn_91c0e7",
        "name": "Dana Reed",
        "email": "dana@example.com",
        "phone": "+15555550123",
        "unit": "Unit 4",
        "lease_id": null
      }
    ],
    "next_cursor": null
  }

• POST

  list_leases

  Leases with unit, tenants, rent, start and end dates and balance due.

  read

  Returns leases with the unit, the tenants on them, monthly rent, dates and the balance due. Filter by status, by end date or by property. Use lease_id from here in the other lease tools. Search matches unit or tenant name.

  POST /api/v1/doorloop/list_leases

  Input

  Input: list_leases

  Parameter	Type	Description
  search	string	Match on unit or tenant name.
  status	enum	active or ended. Default: active.
  ends_before	date	Only leases ending on or before this date.
  property_id	string	Only this property. Property ID from list_properties.
  cursor	string	Next page cursor from the previous call.

  Example response

  {
    "leases": [
      {
        "lease_id": "ls_64f1a9c2",
        "unit": "Unit 2B",
        "property": "Maple Court",
        "tenants": [
          "Marcus Hale"
        ],
        "rent": "1450.00",
        "start_date": "2026-01-01",
        "end_date": "2026-12-31",
        "balance_due": "1450.00"
      }
    ],
    "next_cursor": null
  }

• POST

  get_lease_transactions

  Charges, payments and credits on a lease, oldest first, with the running balance.

  read

  Returns the ledger of one lease, oldest first: charges, payments and credits, each with a running balance. Use it to see whether a rent charge is still open before you add a fee or record a payment.

  POST /api/v1/doorloop/get_lease_transactions

  Input

  Input: get_lease_transactions

  Parameter	Type	Description
  lease_id required	string	Lease ID from list_leases.
  from	date	Start date. Default: lease start.
  to	date	End date. Default: today.

  Example response

  {
    "lease_id": "ls_64f1a9c2",
    "transactions": [
      {
        "type": "charge",
        "date": "2026-10-01",
        "description": "Rent October 2026",
        "amount": "1450.00",
        "balance": "1450.00"
      }
    ],
    "balance_due": "1450.00"
  }

• POST

  list_tasks

  Tasks and work orders with status, due date, property and assignee.

  read

  Returns tasks and work orders, filtered by status or property. Each item has its subject, the property or unit it concerns, the due date and who it is assigned to.

  POST /api/v1/doorloop/list_tasks

  Input

  Input: list_tasks

  Parameter	Type	Description
  status	string	Only tasks with this status, as DoorLoop shows it.
  property_id	string	Only this property. Property ID from list_properties.
  cursor	string	Next page cursor from the previous call.

  Example response

  {
    "tasks": [
      {
        "task_id": "tk_20c8",
        "subject": "Fix hallway light",
        "property": "Maple Court",
        "unit": null,
        "status": "open",
        "due_date": "2026-10-15",
        "assignee": "Sam Ortiz"
      }
    ],
    "next_cursor": null
  }

• POST

  list_communications

  The Communications Log: announcements and messages sent, with channel and delivery status.

  read

  Returns entries from the Communications Log, newest first, with the channel, subject and delivery status. Use it after send_announcement to see who the announcement reached.

  POST /api/v1/doorloop/list_communications

  Input

  Input: list_communications

  Parameter	Type	Description
  since	datetime	Only entries sent after this time.
  cursor	string	Next page cursor from the previous call.

  Example response

  {
    "communications": [
      {
        "communication_id": "cm_77f0",
        "subject": "Water shutoff Thursday",
        "channel": "email",
        "sent_at": "2026-10-11T09:02:00Z",
        "delivery": "delivered",
        "recipients": 12
      }
    ],
    "next_cursor": null
  }

• POST

  create_tenant

  Add a tenant contact, ready to put on a lease. Sends nothing.

  write

  Adds one tenant contact. It sends nothing to the tenant and attaches no charge. It runs without asking first, because it reaches no one and the contact can be deleted in DoorLoop.

  POST /api/v1/doorloop/create_tenant

  Input

  Input: create_tenant

  Parameter	Type	Description
  first_name required	string	First name.
  last_name required	string	Last name.
  email	string	Email address.
  phone	string	Phone number, E.164.

  Example response

  {
    "tenant_id": "tn_91c0e7",
    "name": "Dana Reed",
    "email": "dana@example.com",
    "status": "created"
  }

• POST

  create_task

  New task or work order for a property or unit.

  write

  Creates a task or work order with a subject, optional property or unit and a due date. It does not message anyone by itself. It runs without asking first, because it reaches no tenant and the task can be removed in DoorLoop.

  POST /api/v1/doorloop/create_task

  Input

  Input: create_task

  Parameter	Type	Description
  subject required	string	Short title.
  description	string	Details for whoever does the work.
  property_id	string	Only this property. Property ID from list_properties.
  unit_id	string	Unit it concerns.
  due_date	date	Due date.

  Example response

  {
    "task_id": "tk_20c9",
    "subject": "Replace smoke detector, Unit 2B",
    "property": "Maple Court",
    "due_date": "2026-10-18",
    "status": "created"
  }

• POST

  create_lease

  New lease on a unit with tenants, term, monthly rent and security deposit.

  asks first write

  Creates a lease on one unit in a single step: tenants, term, recurring rent with its due day and an optional security deposit. Leave end_date empty for a month-to-month lease. The lease creates charges on the ledger. By default you confirm each call; you can switch that off for this tool.

  POST /api/v1/doorloop/create_lease

  Input

  Input: create_lease

  Parameter	Type	Description
  unit_id required	string	Unit ID from list_units.
  tenant_ids required	string[]	Tenant IDs from list_tenants or create_tenant.
  start_date required	date	First day of the lease.
  end_date	date	Last day. Leave empty for month-to-month.
  rent required	object	amount and due_day of the recurring rent charge.
  security_deposit	object	amount and due_date.

  Example response

  {
    "lease_id": "ls_9e13b5",
    "unit": "Unit 4",
    "tenants": [
      "Dana Reed"
    ],
    "start_date": "2026-11-01",
    "end_date": "2027-10-31",
    "rent": {
      "amount": "1600.00",
      "due_day": 1
    },
    "security_deposit": {
      "amount": "1600.00",
      "due_date": "2026-11-01"
    },
    "status": "created"
  }

• POST

  post_lease_charge

  One-time charge on a lease, such as a late fee. It shows on the tenant's balance.

  asks first write

  Adds one charge to a lease ledger, for example a late fee or a utility bill. It raises the balance due. It does not change your late fee policy. By default you confirm each call; you can switch that off for this tool.

  POST /api/v1/doorloop/post_lease_charge

  Input

  Input: post_lease_charge

  Parameter	Type	Description
  lease_id required	string	Lease ID from list_leases.
  amount required	string	Decimal amount, e.g. "50.00".
  date required	date	Charge date.
  account required	string	Income account, as named in your DoorLoop chart of accounts.
  memo	string	Shown on the ledger.

  Example response

  {
    "charge_id": "ch_41b7",
    "lease_id": "ls_64f1a9c2",
    "amount": "50.00",
    "date": "2026-10-11",
    "account": "Late Fees",
    "balance_due": "1500.00",
    "status": "posted"
  }

• POST

  record_lease_payment

  Record a payment received outside online payments and apply it to open charges.

  asks first write

  Records a payment on a lease, the same as Receive Payment in DoorLoop, and applies it to open charges. The response lists the charges it was applied to and the balance after. By default you confirm each call; you can switch that off for this tool.

  POST /api/v1/doorloop/record_lease_payment

  Input

  Input: record_lease_payment

  Parameter	Type	Description
  lease_id required	string	Lease ID from list_leases.
  amount required	string	Decimal amount received.
  date required	date	Date received.
  method required	string	Payment method as DoorLoop lists it, e.g. check or cash.
  reference	string	Check number or other reference.

  Example response

  {
    "payment_id": "pm_8d2e71b0",
    "lease_id": "ls_64f1a9c2",
    "amount": "1450.00",
    "method": "check",
    "reference": "1042",
    "applied_to": [
      {
        "charge": "Rent October 2026",
        "amount": "1450.00"
      }
    ],
    "balance_due": "0.00"
  }

• POST

  issue_lease_credit

  Credit a lease, such as a rent concession, lowering the tenant's balance.

  asks first write

  Adds a credit to a lease ledger, which lowers the balance due. Use the memo to record the reason. By default you confirm each call; you can switch that off for this tool.

  POST /api/v1/doorloop/issue_lease_credit

  Input

  Input: issue_lease_credit

  Parameter	Type	Description
  lease_id required	string	Lease ID from list_leases.
  amount required	string	Decimal amount.
  date required	date	Credit date.
  memo	string	Reason, shown on the ledger.

  Example response

  {
    "credit_id": "cr_19a4",
    "lease_id": "ls_64f1a9c2",
    "amount": "100.00",
    "date": "2026-10-11",
    "balance_due": "1350.00",
    "status": "posted"
  }

• POST

  send_announcement

  Announcement to tenants by email, text or tenant portal. Texts use announcement credits.

  asks first write

  Sends an announcement to tenants of the full portfolio or of chosen properties. Email and portal posts are free. Text messages use announcement credits (1 per 160 characters) and are capped at 800 characters. Announcements need DoorLoop's Pro or Premium plan. By default you confirm each call; you can switch that off for this tool.

  POST /api/v1/doorloop/send_announcement

  Input

  Input: send_announcement

  Parameter	Type	Description
  subject required	string	Announcement title.
  body required	string	Message text.
  property_ids	string[]	Only tenants in these properties. Default: all.
  channels required	string[]	Any of email, text, portal.

  Example response

  {
    "communication_id": "cm_77f0",
    "subject": "Water shutoff Thursday",
    "channels": [
      "email",
      "text"
    ],
    "recipients": 12,
    "status": "sent"
  }

Each successful call uses credits for the work it takes; failed calls and timeouts cost nothing. A hard spend cap is on by default. Authenticate with the Authorization: Bearer header.