Propexo Integration¶

MeterBase integrates with property management systems (PMS) through Propexo, a unified API that normalizes data across multiple PMS platforms. This integration enables importing properties, syncing units and leases, and posting RUBS tenant charges directly to your PMS.

What Is Propexo?¶

Propexo is a middleware platform that provides a single, normalized API for interacting with property management systems. Instead of building separate integrations for each PMS, MeterBase connects to Propexo once and gains access to all supported platforms.

Supported PMS Platforms¶

Setup¶

Step 1: Get a Propexo Account¶

Sign up at propexo.com and obtain your API credentials:

• API Key -- Used to authenticate API requests
• Integration ID -- Identifies your Propexo integration

Step 2: Configure MeterBase¶

Add the Propexo credentials to your .env file:

PROPEXO_API_KEY=your-propexo-api-key
PROPEXO_BASE_URL=https://api.propexo.com
PROPEXO_WEBHOOK_SECRET=your-webhook-signing-secret

Step 3: Connect Your PMS in Propexo¶

In the Propexo dashboard:

1. Create a new Connection for your PMS
2. Enter your PMS credentials (Yardi username/password, RealPage API key, etc.)
3. Authorize Propexo to access your PMS data
4. Note the Connection ID -- you will need it in MeterBase

Step 4: Register the Connection in MeterBase¶

curl -X POST https://api.meterbase.io/api/propexo/connections \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "propexo_connection_id": "conn_abc123",
    "pms_type": "yardi",
    "name": "Yardi - West Coast Portfolio"
  }'

Import Properties from PMS¶

Once connected, import properties from your PMS into MeterBase:

# List available properties from PMS
curl "https://api.meterbase.io/api/propexo/connections/1/properties" \
  -H "Authorization: Bearer $TOKEN"

# Import selected properties
curl -X POST https://api.meterbase.io/api/propexo/import-properties \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "connection_id": 1,
    "portfolio_id": 1,
    "propexo_property_ids": ["prop_001", "prop_002", "prop_003"]
  }'

Imported properties automatically include:

• Property name and address
• Unit count
• Square footage (if available in the PMS)
• Automatic utility lookup by ZIP code

Sync Units and Leases¶

After importing properties, sync unit-level data for RUBS calculations:

curl -X POST https://api.meterbase.io/api/propexo/sync-units \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"property_id": 1}'

This pulls from the PMS:

The Billing Flow¶

The complete PMS-connected RUBS workflow:

Charge Posting¶

Posting RUBS charges back to the PMS is the most critical part of the integration. Here is how it works in detail.

How It Works¶

1. Job creation -- When you confirm RUBS charges for posting, MeterBase creates an async charge posting job.
2. Per-unit posting -- The background worker iterates through each unit's charge and posts it to the PMS via Propexo.
3. Charge code mapping -- Each charge is posted with a configurable charge code (e.g., UTIL, RUBS, ELEC) that maps to your PMS's chart of accounts.
4. Confirmation tracking -- Propexo returns a charge ID for each posted charge. MeterBase stores this for audit and deduplication.
5. Error handling -- If a charge fails to post (e.g., the resident moved out, the unit does not exist in the PMS), it is flagged for manual review.

Charge Posting Request¶

curl -X POST https://api.meterbase.io/api/rubs/post-charges \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "property_id": 1,
    "bill_id": 42,
    "charge_date": "2026-04-01",
    "charge_code": "UTIL",
    "description": "March 2026 Utility Charge (RUBS)",
    "post_to_pms": true
  }'

Job Status¶

Monitor the charge posting job:

curl "https://api.meterbase.io/api/rubs/post-status/job_abc123" \
  -H "Authorization: Bearer $TOKEN"

Response:

{
  "job_id": "job_abc123",
  "status": "completed",
  "total_charges": 45,
  "posted": 44,
  "failed": 1,
  "failures": [
    {
      "unit": "304",
      "amount": 142.50,
      "error": "Resident lease expired. No active lease found for unit 304.",
      "propexo_error_code": "LEASE_NOT_FOUND"
    }
  ]
}

Deduplication¶

MeterBase prevents duplicate charges through multiple safeguards:

• Each RUBS calculation is associated with a specific bill ID and billing period
• The system checks for existing charges for the same bill/period before posting
• Propexo returns unique charge IDs that are stored locally for reference
• A confirmation step in the UI shows if charges for this period have already been posted

Webhook Support¶

Propexo can send webhooks to MeterBase for real-time updates. See the Webhook Guide for full details.

Key webhook events:

Data Model Mapping¶

How Propexo fields map to MeterBase fields:

Properties¶

Units¶

Charges (Outbound)¶

Troubleshooting¶

Connection fails to validate¶

• Verify your Propexo API key is correct in .env
• Ensure the Propexo Connection ID matches an active connection in the Propexo dashboard
• Check that the PMS credentials in Propexo are still valid (passwords may have expired)

Properties not appearing for import¶

• The PMS connection may still be syncing. Initial sync can take 5-30 minutes depending on portfolio size.
• Check the Propexo dashboard for sync status and errors.
• Some PMS platforms require specific permissions to expose property data via API.

Unit data is incomplete¶

• Not all PMS platforms expose every field. Square footage and occupant count may be unavailable.
• Check the PMS configuration to ensure unit-level data fields are populated.
• For missing sqft, enter values manually in MeterBase or import via CSV.

Charge posting fails¶

Sync is slow or timing out¶

• Large portfolios (500+ properties) may take 30-60 minutes for initial sync
• Set PROPEXO_SYNC_INTERVAL to a reasonable value (3600+ seconds) to avoid excessive API calls
• For very large portfolios, sync during off-peak hours