ResMan

Supergood | ResMan API

Alex Klarfeld

Alex Klarfeld

— 7 min read
Supergood | ResMan API

Programmatically access ResMan property, unit, leasing, resident ledger, and maintenance data with a stable REST API. Supergood builds and operates production-grade, unofficial ResMan integrations so your team can automate portfolio operations without heavy custom engineering.

Plain English: ResMan is property management software for multifamily operators (conventional, affordable, and student housing) that centralizes leasing, accounting, maintenance, and resident communications. An unofficial API lets you programmatically pull properties, units/availability, prospects/applications, leases and households, resident ledgers and payments, vendors and purchase orders, and work orders—and push new records or updates back into ResMan.

For a tech company integrating with ResMan, this means you can ingest real-time portfolio, unit, and lease data to power dashboards; sync charges, payments, and deposit batches to accounting (e.g., QuickBooks, Xero); automate application and move-in workflows from your product; or enrich your platform with maintenance tickets, photos, and status updates. You can also trigger resident communications, create payment requests, post offline receipts, and keep stakeholder systems (ERP, analytics, CRM, scheduling) in lockstep.

What is ResMan?

ResMan (https://www.myresman.com/) is a cloud platform for multifamily property management that connects front-office leasing, back-office accounting, maintenance, and resident portals across management teams, residents, prospects, and vendors. Operators use ResMan to market units, manage applications and screenings, execute and renew leases, collect online payments, post charges and late fees, track vendor bills and purchase orders, and manage maintenance and turns—with robust reporting and affordable housing compliance modules.

Core product areas include:

  • Leasing & CRM (Prospects, Guest Cards, Applications, Screenings, Renewals)
  • Property & Unit Management (Properties, Buildings, Units, Floorplans, Availability)
  • Resident Experience (Resident Portal, Online Payments, Requests, Communications)
  • Maintenance & Turns (Work Orders, Inspections, Make-Ready Boards, Photos/Documents)
  • Accounting (GL, AP/AR, Charge Codes, Vendor Bills, Purchase Orders, Bank Recs)
  • Compliance (Affordable/HUD/LIHTC, Certifications, HAP/Household Data)

Common data entities:

  • Companies, Portfolios, Properties (address, bank accounts, GL segments)
  • Units & Floorplans (attributes, market rent, amenities, status/availability)
  • Prospects & Applications (contact info, screening status, source)
  • Leases/Households (primary resident, roommates, occupants, pets/vehicles)
  • Charges & Payments (codes, recurring charges, ledgers, deposits, batches)
  • Vendors & Purchase Orders (commitments, invoices, approvals)
  • Work Orders (category, priority, labor/materials, photos, completion)

The ResMan Integration Challenge

Multifamily teams rely on ResMan for daily operations, but turning portal-based workflows into API-driven automation is non-trivial:

  • Role-aware portals: Staff, residents, prospects, and vendors each see different data, ledgers, and actions
  • Accounting rigor: Trust accounting, deposits, recurring charges, proration rules, and late fee policies must be applied consistently; affordable housing adds HUD/LIHTC compliance nuance
  • Portal-first features: Online application, screening, payment, and maintenance flows are optimized for front-end experiences rather than headless automation
  • Authentication complexity: SSO (e.g., Azure AD) and MFA can complicate unattended integrations; sessions may expire with frequent challenges
  • Data spread & exports: Key objects span units, leases, ledgers, and maintenance; teams often report limited bulk exports, partner-gated APIs, or costly access, pushing them toward scheduled CSVs and manual reports
  • Property segmentation: IDs, charge codes, and permissions can differ by property or portfolio, making normalization and multi-entity reporting tricky

How Supergood Creates ResMan APIs

Supergood reverse-engineers authenticated browser flows and network interactions to deliver a resilient API endpoint layer for your ResMan environment.

  • Handles username/password, SSO/OAuth, and MFA (SMS, email, TOTP) securely
  • Maintains session continuity with automated refresh, captcha/challenge handling, and change detection
  • Normalizes responses so you can integrate once and rely on consistent objects across modules
  • Aligns with customer entitlements and role-based permissions to ensure compliant access
  • Orchestrates long-running tasks (e.g., report exports) and converts them into synchronous or webhook-driven APIs

Use Cases

Property, Unit & Resident Sync

  • Mirror properties, buildings, units, and floorplans with availability into your internal systems
  • Keep household and lease metadata current for analytics and resident experiences
  • Normalize addresses, statuses, and charge codes across portfolios

Leasing & Move-In Automation

  • Create applications or pending leases from your product and trigger e-signature workflows
  • Apply proration and recurring charge schedules consistently
  • Update lease status, renewals, and household changes programmatically

Maintenance & Field Ops

  • Create work orders from IoT/sensor alerts or your mobile app
  • Attach photos/documents, update status and assignments, and capture completion details
  • Sync task metrics to a BI warehouse for SLA reporting

Financials: Charges, Payments, and Accounting Sync

  • Post offline receipts and reconcile resident ledgers
  • Pull charges and payments to reconcile with accounting (e.g., QuickBooks, Xero)
  • Map charge codes and deposit batches to your GL structure and push summaries to your ERP

Available Endpoints

Authentication

POST /sessions: Establish a session using credentials. Supergood manages MFA (SMS, email, TOTP) and SSO/OAuth when enabled. Returns a short-lived auth token maintained by the platform.

curl --request POST \
  --url https://api.supergood.ai/integrations/<integration_id>/sessions \
  --header 'Authorization: Basic <Base64 encoded token>' \
  --header 'Content-Type: application/json' \
  --data '{
    "username": "[email protected]",
    "password": "<password>",
    "mfa": { "type": "totp", "code": "123456" }
  }'

Example response

{
  "authToken": "eyJhbGciOi...",
  "expiresIn": 3600,
  "user": {
    "id": "u_resman_381c22",
    "name": "Leasing Coordinator",
    "entitlements": ["properties", "units", "leases", "ledgers", "work_orders"]
  }
}

Properties

GET /properties: List properties with filters and summary details.

Query parameters

  • portfolioId: string
  • status: active | inactive | archived
  • updatedFrom, updatedTo: ISO 8601 timestamps
  • page, pageSize: integers for pagination

Example response

{
  "items": [
    {
      "propertyId": "prop_6f12a9",
      "name": "Maple Grove Apartments",
      "code": "MAPL-GRV",
      "status": "active",
      "marketType": "conventional",
      "address": {
        "line1": "1450 W Maple St",
        "city": "Plano",
        "region": "TX",
        "postalCode": "75024",
        "country": "US"
      },
      "unitSummary": {
        "totalUnits": 220,
        "vacant": 18,
        "onNotice": 7,
        "occupied": 195
      },
      "occupancyRate": 0.886,
      "updatedAt": "2026-01-18T15:42:10Z"
    }
  ],
  "page": 1,
  "pageSize": 50,
  "total": 1
}

Units

GET /properties/{propertyId}/units: List units and availability with filters.

Query parameters

  • status: vacant | occupied | on_notice | make_ready | down
  • bedrooms: integer
  • bathrooms: number
  • rentMin, rentMax: numbers
  • updatedFrom, updatedTo: ISO 8601 timestamps
  • page, pageSize: integers for pagination
curl --request GET \
  --url "https://api.supergood.ai/integrations/<integration_id>/properties/prop_6f12a9/units?status=vacant&page=1&pageSize=50" \
  --header 'Authorization: Bearer <authToken>'

Example response

{
  "items": [
    {
      "unitId": "unit_2b9d70",
      "number": "12B",
      "floorplan": "2x2 A",
      "bedrooms": 2,
      "bathrooms": 2,
      "sqft": 980,
      "floor": 1,
      "status": "vacant",
      "marketRent": 1599.00,
      "availableDate": "2026-02-05",
      "amenities": ["Washer/Dryer", "Balcony"],
      "currentLeaseId": null,
      "updatedAt": "2026-01-19T09:10:03Z"
    }
  ],
  "page": 1,
  "pageSize": 50,
  "total": 12
}

Leases

POST /properties/{propertyId}/leases: Create a pending lease with household members, deposits, and recurring charges. Supports proration and e-signature initiation.

curl --request POST \
  --url https://api.supergood.ai/integrations/<integration_id>/properties/prop_6f12a9/leases \
  --header 'Authorization: Bearer <authToken>' \
  --header 'Content-Type: application/json' \
  --data '{
    "unitId": "unit_2b9d70",
    "leaseStartDate": "2026-02-10",
    "leaseEndDate": "2027-02-09",
    "prorationMethod": "actual_days",
    "primaryResident": {
      "firstName": "Ariel",
      "lastName": "Nguyen",
      "email": "[email protected]",
      "phone": "+1-555-212-9988"
    },
    "householdMembers": [
      {"firstName": "Jordan", "lastName": "Ramirez", "relationship": "roommate"}
    ],
    "deposits": [
      {"type": "security", "amount": 500.00}
    ],
    "recurringCharges": [
      {"chargeCode": "RENT", "amount": 1599.00, "frequency": "monthly", "startDate": "2026-02-10"},
      {"chargeCode": "PARK", "amount": 50.00, "frequency": "monthly", "startDate": "2026-02-10"}
    ],
    "requiresESignature": true,
    "referenceId": "crm-opp-4412",
    "notifyResident": true
  }'

Example response

{
  "leaseId": "lea_94d0c1",
  "status": "pending_signature",
  "unitId": "unit_2b9d70",
  "householdSize": 2,
  "monthlyTotal": 1649.00,
  "createdAt": "2026-01-20T14:22:11Z"
}

Payments

POST /payments: Post an offline resident payment and allocate to open charges on the ledger. For online ACH/card flows, Supergood can initiate tokenized payment requests where enabled.

curl --request POST \
  --url https://api.supergood.ai/integrations/<integration_id>/payments \
  --header 'Authorization: Bearer <authToken>' \
  --header 'Content-Type: application/json' \
  --data '{
    "propertyId": "prop_6f12a9",
    "leaseId": "lea_94d0c1",
    "residentId": "res_11f3c9",
    "amount": 1649.00,
    "currency": "USD",
    "method": "check",
    "receivedDate": "2026-03-01",
    "reference": "CK#1042",
    "allocations": [
      {"chargeCode": "RENT", "amount": 1599.00},
      {"chargeCode": "PARK", "amount": 50.00}
    ],
    "notes": "March rent + parking received at office",
    "depositBatch": {
      "batchDate": "2026-03-01",
      "bankAccountId": "bank_781aa2"
    }
  }'

Example response

{
  "paymentId": "pay_77c3b0",
  "status": "posted",
  "total": 1649.00,
  "applied": 1649.00,
  "unapplied": 0.00,
  "depositBatchId": "dep_5b9120",
  "createdAt": "2026-03-01T16:05:49Z"
}

Get full API Specs →

Technical Specifications

  • Authentication: Username/password with MFA (SMS, email, TOTP) and SSO/OAuth where enabled; supports service accounts or customer-managed credentials
  • Response format: JSON with consistent resource schemas and pagination across modules
  • Rate limits: Tuned for enterprise throughput while honoring customer entitlements and usage controls
  • Session management: Automatic reauth and cookie/session rotation with health checks and challenge solving
  • Data freshness: Near real-time retrieval of properties, units, leases, ledgers/payments, and maintenance objects
  • Security: Encrypted transport, scoped tokens, and audit logging; respects ResMan role-based permissions and PCI considerations for payment flows
  • Webhooks: Optional asynchronous delivery for long-running workflows (e.g., payment confirmations, lease signatures, unit status changes)

Performance Characteristics

  • Latency: Sub-second responses for list/detail queries under normal load
  • Throughput: Designed for high-volume unit/lease sync and payment posting
  • Reliability: Retry logic, backoff, and idempotency keys minimize duplicate actions
  • Adaptation: Continuous monitoring for UI/API changes with rapid adapter updates

Getting Started

  1. Schedule Integration Assessment

Book a 30-minute session to confirm your modules, licensing, and authentication model.

  1. Supergood Builds and Validates Your API

We deliver a hardened ResMan adapter tailored to your workflows and entitlements.

  1. Deploy with Monitoring

Go live with continuous monitoring and automatic adjustments as ResMan evolves.

Schedule Integration Call →

Frequently Asked Questions

Q: Which ResMan modules can this integration cover?

Supergood supports workflows across commonly used modules such as Leasing & CRM (Prospects, Applications, Screening statuses), Property & Unit data, Resident Experience (Ledgers, Online Payments), Maintenance (Work Orders, Photos), and Accounting (Charges, Recurring Schedules, Vendor Bills/POs) subject to your licensing and entitlements. We scope coverage during integration assessment.

Q: How are MFA and SSO handled for automation?

We support username/password + MFA (SMS, email, TOTP) and can operate behind SSO/OAuth when enabled. Sessions are refreshed automatically with secure challenge handling and monitoring for session health.

Q: Can you sync charges and payments to our accounting system?

Yes. We can normalize charges, payments, and deposit batches to match your ERP/accounting schema (e.g., charge codes, classes, taxes) and deliver updates via webhooks or polling while complying with rate and permission constraints. We commonly integrate with QuickBooks and Xero.

Q: Can you work with affordable housing/LIHTC data?

We can ingest household certifications and compliance statuses and align those with leases and charges. Support depends on your ResMan modules and permissions; we confirm coverage during scoping.

AppFolio API — Programmatically access AppFolio property data with Supergood

Ready to automate your ResMan workflows?

Supergood can have your ResMan integration live in days with no ongoing engineering maintenance.

Get Started →

Read more