canonical: https://jentic.com/apis/realpage.com/realpage

# RealPage Exchange API

The RealPage Exchange (RPX) API enables integration with RealPage's property management platform. The API provides access to resident management, lease tracking, property operations, and financial data. Access requires an active RealPage partner agreement through the RPX AppPartner Program. The API supports both REST and SOAP interfaces; this specification covers the REST API endpoints. The API exposes 14 endpoints secured with apiKey, basic authentication.

## For AI agents

Programmatically list residents, get resident details. Covers 14 operations with apiKey, basic authentication.

## Scope

Does not handle payments, communications, or developer tools - use for crm only.

## Capabilities

- List residents
- Get resident details
- Access RealPage Exchange API crm resources via REST API

## Use cases

### CRM Operations

Use the RealPage Exchange API to perform crm operations programmatically. The API provides 14 endpoints covering core functionality including list residents, get resident details, get resident events.

Example prompt: Call GET /residents to list residents

### Automated Residents Management

Automate residents operations by combining multiple RealPage Exchange API endpoints. Agents can get resident details and then get resident events in a single workflow.

Example prompt: Call GET `/residents/{residentId}` to get resident details, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call RealPage Exchange API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey, basic tokens manually.

Example prompt: Search Jentic for 'list residents', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/residents` | List residents |
| GET | `/residents/{residentId}` | Get resident details |
| GET | `/residents/events` | Get resident events |
| GET | `/leases` | List leases |
| GET | `/leases/{leaseId}` | Get lease details |
| GET | `/sites` | List sites |
| GET | `/sites/{siteId}` | Get site details |
| GET | `/sites/{siteId}/units` | List units for a site |

## Key resources

- **Residents** — Resident management and event tracking
- **Leases** — Lease management operations
- **Sites** — Site (property) management
- **Units** — Unit management operations
- **Financials** — Charges and payment operations

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 58 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 44 / 100
  - Agent Usability: 94 / 100
  - Security: 30 / 100
  - AI Discoverability: 79 / 100
- **View full report:** https://jentic.com/apis/realpage.com/realpage/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the RealPage Exchange API by hand means combining its X-License-Key header with HTTP basic auth, navigating residents, leases, sites, and units, and handling paging and retries yourself. Through Jentic you install once, import the RealPage Exchange API from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** The RealPage Exchange API puts the site id in the URL path (`/sites/{siteId}/units`), so a rule can pin your agent to one site. You choose the operations it may call, and since these endpoints are read-only, it retrieves residents, leases, and units rather than changing them.
- **Credential handling:** Your RealPage Exchange API credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list residents' or 'get units for a site', and Jentic returns the matching RealPage Exchange API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Hubspot** — Alternative crm API
- **Salesforce** — Alternative crm API
- **Pipedrive** — Complementary crm API
- **Zoho** — Complementary crm API

## FAQ

### What authentication does the RealPage Exchange API use?

The RealPage Exchange API uses apiKey, basic authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I list residents with the RealPage Exchange API?

Yes. Use the GET /residents endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the RealPage Exchange API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I list residents through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list residents'. Jentic returns the matching RealPage Exchange API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the RealPage Exchange API have?

The RealPage Exchange API exposes 14 endpoints covering residents, leases, sites operations.

### Can I limit what my agent is allowed to do with the RealPage Exchange API?

Yes. Because Jentic One is self-hosted, your own rules decide which RealPage Exchange API operations and credentials your agent may use. Since the site id lives in the URL path (`/sites/{siteId}/units`), you can pin the agent to a single site, and you pick exactly which operations it may call, such as GET /residents, GET /leases, or GET `/sites/{siteId}/units.` These endpoints are read-only, so the agent retrieves resident, lease, and unit data rather than changing it.